Doesn't XDoclet defeat the basic purpose of having deployment descriptors?
3 posts in topic
Flat View  Flat View
TOPIC ACTIONS:
 

Posted By:   Sathish_Kumar
Posted On:   Friday, February 21, 2003 03:55 PM

The whole concept of deployment descriptors came up for seperating the code from the deployment details. You use CMP's so that the mappings to the underlying schema and SQL's for the finders are taken out of the code.

Doesn't XDoclet defeat this basic purpose itself?

Re: Doesn't XDoclet defeat the basic purpose of having deployment descriptors?

Posted By:   Anonymous  
Posted On:   Monday, March 17, 2003 07:54 AM

The idea of vendor specific deployment descriptors is not a basic idea of java and j2ee: build once, run everywhere.

Re: Doesn't XDoclet defeat the basic purpose of having deployment descriptors?

Posted By:   Chuck_Lan  
Posted On:   Friday, February 28, 2003 12:09 PM

Well, I look at XDoclet as a development tool. As of now, it is capable of generating home/remote interfaces, as well as deployment descriptor files, to make life simpler for you. The descriptor files are still available for modification.

Re: Doesn't XDoclet defeat the basic purpose of having deployment descriptors?

Posted By:   Javed_Mandary  
Posted On:   Friday, February 21, 2003 09:57 PM


Xdoclet is just a code generation tool mate, it simplies your life in that you only have to write you business logic into you Bean , tag out what you want and it generates all your deployment descriptors, Local,Remote interafaces for you.

If what you are asking for is to come true , you should address yourself to EJB container developpers of JBoss , Websphere, Orale9AS, etc.. It is these folks that implemented the idea of deployment descriptors to capture mappings of files and objects in the first place

Javed

Mauritius

http://www.baadaal.tk
About | Sitemap | Contact