On 2001.12.11 14:46:49 -0500 Ean Schuessler wrote: > Something I don't understand about xdoclet. Doesn't putting the ejb-jar > configuration information into your source code sort of defeat the > purpose of having a deployment descriptor? I thought that the whole idea > was to decouple the configuration from the source.
Personally, I've hardly used xdoclet (may change soon;-)) I think the generation of home and remote and local and local-home interfaces is universally and unconditionally a good idea. Generation of config files seems to me to imply that each ejb will be deployed using only one dd. This is presumably by far the most frequent case, and for that it makes a lot of sense. Generating all the dd's for different app servers seems pretty useful too. So, my current uninformed optinion is that it makes the most frequent use really easy, and provides something to modify for other cases when you need to deploy the same codebase as several ejbs. I think it is mostly targeted at ejb development, where one person is filling all those roles at once. If you have a separate deployer-person, at least it gives you somewhere to start. david jencks > > On Tue, 2001-12-11 at 11:00, David Jencks wrote: > > Is there a reasonably simple way to make xdoclet only run if one of the > files it is processing has changed? Most of the time for my server > module builds seems to be taken with xdoclet, and I never change stuff it > starts with. > > -- > _____________________________________________________________________ > Ean Schuessler [EMAIL PROTECTED] > Brainfood, Inc. http://www.brainfood.com > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
