Hi Ara, In fact, I tried to use a BMP, and it fails because as you can see in entitybmp.j, when you are using Ejbspec=2.0, it generate an abstract class:
>>>From entitybmp.j: public <XDoclet:ifConfigParamEquals paramName="Ejbspec" value="2.0">abstract </XDoclet:ifConfigParamEquals>class <XDoclet:classOf><XDoclet:entityBmpClass/></XDoclet:classOf> extends <XDoclet:fullClassName/> implements javax.ejb.EntityBean<XDoclet:ifHasClassTag tagName="ejb:bean" paramName="remote-business-interface">, <XDoclet:classTagValue tagName="ejb:bean" paramName="remote-business-interface" /></XDoclet:ifHasClassTag><XDoclet:ifHasClassTag tagName="ejb:bean" paramName="local-business-interface">, <XDoclet:classTagValue tagName="ejb:bean" paramName="local-business-interface" /></XDoclet:ifHasClassTag> <<< >>> generated BMP: /** * * @xdoclet-generated at 17-oct.-01 21:28:25 */ public abstract class ArticleRenditionBMP extends com.synegorie.articles.ejb.ArticleRenditionBean implements javax.ejb.EntityBean <<< And also there are no fields variables defined nor are concrete getter/setters. I just checked out the last version of entitybmp.j from CVS, to be sure. So I restate my question: 1? XDoclet impose abstract BMP entities when you use ejbspec="2.0". 2? There are no equivalent to the 'cmp-version="1.x"' for BMP Beans. 3? I'm using abstract getter/setters in my Bean classes. 4? I would like to get XDoclet support for Data Objects, and Store optimisations, ... 5? I'm targeting cmp 1.x (jBoss 2.4) ==> As jBoss 2.4.1, AFAIK, doesn't support abstract BMP Beans: how do I convince XDoclet to generate a concrete class for a BMP bean. If I modify the template (entitybmp.j) to test for another condition (for the test, I used ifUsingCmp2/ifNotUsingCmp2), I get a concrete class. So, is it the way to go ? Or am I wrong with abstract BMP support in jBoss ? Sorry for such a long mail, Francois Duchatelet, Manager, Synegorie SA Bvd du Midi, 25-27/rue Bodeghem, 91-93 B-1000 Brussels Mobile:+32(486)13.07.85 TEL:+32(2)502.96.98 - FAX:+32(2)503.19.32 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Ara Abrahamian Sent: Wednesday, October 17, 2001 7:07 PM To: 'Francois Duchatelet'; [EMAIL PROTECTED] Subject: RE: [Xdoclet-user] BMP and Ejbspec = 2.0 > When you switch to Ejbspec 2.0 (the default anyway), you are generating > abstract classes for BMP entities. For CMP entities actually. For bmp in ejb1.1 and ejb2 xdoclet generates concrete getter/setters in generated class. > You don't have the choice, as for CMP beans, to generate concrete classes. > > Is it so in the EJB specs ? Yup, Ejb 2 uses abstract schema concept. > Shall I need to patch heavilly the templates to have something "bmp=1.x" ? What are you trying to do? Regardless of entity type or ejbspec version you declare getter/setter methods of your entity abstract. It's actually interesting; you can target ejb1.1 and migrate to ejb2 easily by using xdoclet. For many toolkit and framework providers who have to deliver products to say websphere 4 (ejb 1.1) and weblogic 6.x (ejb2) this is very useful. Unfortunately nowhere in docs we documented it :o) Ara. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
