Jonathan, I have run into this issue as well. Please see my posts from the Spring. My research revealed that the OpenEJB XDoclet implementation was indeed for version 1.0 of OpenEJB. I did not find a release for version 2.0 of OpenEJB.
Not having the openejb-jar.xml mappings generated from the source did make managing my Entity Beans a little harrier. I was able to generate the ejb-jar.xml from the XDoclet annotations, but had to hand develop the openejb-jar.xml from scratch. It worked, but I'd love to be able to plug-in an XDoclet module and have the base openejb-jar.xml generated. It whould serve as an initial source for a deployment tool utilized by a Server Administrator. That enables clear seperation of developer and administrator duties, while offering codebase stability and deployment flexibility. Mark Aufdencamp [EMAIL PROTECTED] > -------- Original Message -------- > Subject: Using XDoclet to generate openejb-jar.xml > From: Jonathan Gallimore <[EMAIL PROTECTED]> > Date: Tue, August 14, 2007 7:28 am > To: [email protected] > > Hi All, > > Apologies if this has been asked before, but I was wondering whether > anyone uses XDoclet to generate their openejb-jar.xml deployment > descriptors? > > Currently we're developing for JBoss 4, and are part way through getting > our app to deploy on the community edition of Websphere. The J2G > migration tool has done an excellent job of migrating our deployment > descriptors, but going forward I'd still like to add all the necessary > XML stuff for new EJBs using XDoclet rather than hand editing the > openejb-jar.xml. Having hunted around it looks like the openejb task > that comes with XDoclet is for a much older version, and only handles > session beans. > > I've started work on an xdoclet plugin that generates a basic > openejb-jar.xml for me, and I was just wondering whether I had missed an > existing tool/plugin and was just duplicating work (obviously if I > haven't and this is a useful piece of work, I'd be happy to continue and > share it). > > I'd appreciate any thoughts anyone has. > > Regards, > > Jon
