Thanks for that info. I am in the process of rebuilding the xdoclet support so that it covers all versions, but have not announced anything yet (guess this kind of is now) until I get my build environment up and running. Have basic support working for my test bean and thats about it, this info will help get a lot more going. Nicholas Irving [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
________________________________ From: David Blevins [mailto:[EMAIL PROTECTED] Sent: Fri 29/07/2005 03:49 To: [email protected] Subject: Re: [openejb-user] XDoclet & OpenEJB On Jul 27, 2005, at 5:00 PM, Nicholas Irving wrote: > I have something working with the plugin, but it only seems to have > limited support. The important thing I have found is adding > > * @openejb > > to my Bean source. Working on it though and adding more support as > I believe the document states it only supports Session and not > Entity, also no support for OpenEjb2.0. This is really strange because the cmp support in 1.0 and below is through castor, which does have a full suite of xdoclet tags. It seems the xdoclet cmp support would have been fairly easy to introduce. Regardless, the option does exist to generate the openejb-jar.xml once and just keep reusing it. You really only need to change it if you add/remove beans, change class names, add/remove data sources, or add/remove finder methods. In the case of finder methods, the actual data in the openejb-jar.xml is an OQL query string that can't be generated for you as the reflection API only shows us findByFoo(String,String,int) and not something that could be used to hint the database field names like findByFoo(String firstName, String lastName, int age). If that data was in xdoclet tags or annotations, we could generate the query string for most people. Anyway, if you get the urge to improve the xdoclet support, checkout these links: http://www.openejb.org/faq_openejb-jar.html http://www.openejb.org/faq_cmp.html#finders -David
