<snip> > 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. > > I do not agree :O > The [b]merging[/b] feature of xdoclet permits to do > almost everything in multi deployment mode. It has > really turned xdoclet from a developement tool to > also a deployment tool. Personnally I deploy on > different environments and never change a XML file by > hand. Here's my chance to get some good info on xdoclet from an expert ;-)
1. Looking at the docs for xdoclet it looks to me as if the merge stuff lets you easily construct a complete dd. I was talking about deploying the same java class(es) under several jndi names, with say mappings to several database tables. Is this possible? 2. Is there some way to use xdoclet with a package of ejb's you buy where you don't get the source code? I thought it started with source code and generated the complete deployable package that will work on many app servers without further modification. That's why I was talking about role separation. If you are forced to start with binary classes and an existing ejb-jar.xml does it help you? ______________________________________________________________________ View this jboss-dev thread in the online forums: http://jboss.org/forums/thread.jsp?forum=66&thread=5471 _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
