• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

tools for generation deployment descriptors

 
Subramanian A.S
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Is there any tool for generating deployment descriptors automatically. i.e if i provide the jar file it should generate ejb-jar.xml and weblogic-ejb-jar.xml. similarly for web.xml. please help
 
Lasse Koskela
author
Sheriff
Posts: 11962
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
WebLogic has a tool called DDInit.
 
Vedhas Pitkar
Ranch Hand
Posts: 445
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Check out the RI from Sun where you just have to give the class files,all others are generated by the server.
 
Subramanian A.S
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Lasse Koskela:
WebLogic has a tool called DDInit.

dd's are generated by DDInit??
 
Lasse Koskela
author
Sheriff
Posts: 11962
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
dd's are generated by DDInit??

That's what the docs say. For example, the documentation of EJBInit (part of DDInit) says:
Target a JAR file or a folder containing files that you intend to archive as a JAR file, and EJBInit will generate the ejb-jar.xml and the weblogic-ejb-jar.xml files for the module.
 
Karthik Guru
Ranch Hand
Posts: 1209
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Subramanian A.S:
Is there any tool for generating deployment descriptors automatically. i.e if i provide the jar file it should generate ejb-jar.xml and weblogic-ejb-jar.xml. similarly for web.xml. please help

Now that you are lookign for a tool, why dont you check out XDoclet to generate the deployment descriptors. Looks like a real cool thing to experiment with.
 
Lasse Koskela
author
Sheriff
Posts: 11962
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Does XDoclet generate a valid web.xml or ejb-jar.xml if your source code doesn't have any XDoclet tags in their javadocs?
 
Karthik Guru
Ranch Hand
Posts: 1209
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Never used it myself. But i am *almost* certain that they work on the tags that we attach as comments to the Bean file. S'd be able to generate web.xml file as well.(not sure here, but sd'nt be a big deal for them).
The biggest advantage , i guess, is the way it can be integrated into the daily builds. I mean I dont have to worry about the bean and the descriptors/ interfaces to be in sync. The only code that gets checked into the source control is the bean and nothing else. Run build, generate descriptors, interfaces and ofcourse do a ejbc equivalent and move on.
I guess they generate value objects as well. I agree, so do IDEs, but the fact that i dont need to check in any of the code into the source control + XDoclet's integration with ANT makes it appear so cool to me. There should be lots of other interesting stuff that it offers. I mean yeah, more the generated code , faster is the development.
The authors , i guess are experts on using this tool. Some day i will check it out for sure!
 
Lasse Koskela
author
Sheriff
Posts: 11962
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I know XDoclet works on the javadoc tags. What I was wondering whether XDoclet creates a "default" web.xml/ejb-jar.xml for source code that has no XDoclet tags.
For example, if I have three servlets will the web.xml (if it is generated at all in the absence of any XDoclet-tagged source code) contain URL-mappings for all of them using "servlet/<class name>" or something similar as a default pattern?
Anyway, I'll post this question to the "Other Open Source Projects" forum...
 
Pradeep bhatt
Ranch Hand
Posts: 8933
Firefox Browser Java Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
What I was wondering whether XDoclet creates a "default" web.xml/ejb-jar.xml for source code that has no XDoclet tags.

I guess not.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic