• Post Reply Bookmark Topic Watch Topic
  • New Topic

xdoclet for cross-system compatibility  RSS feed

 
Jim Rock
Ranch Hand
Posts: 39
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Do you think xdoclet is a viable way to make your EJBs runnable on different J2EE configurations?
 
Eric Pascarello
author
Rancher
Posts: 15385
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
This is posted in the wrong forum. It will be moved in a short time to the corretc forum.
 
Karthik Guru
Ranch Hand
Posts: 1209
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Jim Rock:
Do you think xdoclet is a viable way to make your EJBs runnable on different J2EE configurations?

never used it myself. But, are'nt we supposed to use container specific descriptor tags to make XDoclet generate container specfic descriptor files / etc? then the resulting ear can be ported to the specific container.
Not sure how seamless it is though.
 
norman richards
Author
Ranch Hand
Posts: 367
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Jim Rock:
Do you think xdoclet is a viable way to make your EJBs runnable on different J2EE configurations?

What do you mean by "different J2EE configurations". If you mean multiple application servers, XDoclet provides container specific attributes you can use for each app server.
If you mean being able to create multiple ear files for the same app server but with slightly different deployment options, then the answer depends. If the configurations just differ by the values of XDoclet attributes (different values for a security role or servlet init parameter) then you can use ant properties in your XDoclet attributes to drive that.
Of course there are other possible things you could mean. If you are more specific, I'm sure you'll get more specific responses...
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!