Put a @ejb:bean generate="false" in base. See PersonBean in samples, it's an abstract bean, no entry in deployment file is generated for this bean. Xdoclet can not rely on abstract keyword because all bean are by default abstract, xdoclet generates a concrete one for you. We'll make <entitycmp>/etc (those subtasks that generate the concrete classes deriving from your beans) optional, so thereafter we can check the abstract keyword and ignore abstract classes.
Ara. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:xdoclet-user- > [EMAIL PROTECTED]] On Behalf Of Clarance Howatt > Sent: Thursday, November 01, 2001 3:34 AM > To: 'Dmitri Colebatch'; Clarance Howatt > Cc: [EMAIL PROTECTED] > Subject: RE: [Xdoclet-user] Problems upgrading from version 1.0 - current > > Thanks for the quick response. The workaround that you speak of is what I > am doing. It was what was working in 1.0 and is now broken. > > C. > > > -----Original Message----- > From: Dmitri Colebatch [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, October 31, 2001 4:04 PM > To: Clarance Howatt > Cc: [EMAIL PROTECTED] > Subject: Re: [Xdoclet-user] Problems upgrading from version 1.0 - > current > > > Clarance, > > is it a bug or functionality? its definately known about. Just recently > we've been having a discussion on dev about these sorts of issues. I'm > assuming you would like XDoclet to completely ignore any ejbs without > @ejb:bean comments? Another option we've considered is to generate stuff > based on a set of "smart defaults". > > To be honest, I didn't know this had changed since 1.0 (I thought it > changed before that). The only work-around I can suggest is to change > your build.xml to exclude the base bean(s). > > As a side note though - XDoclet will generate whatever methods are > required for the ejbspec (empty implementations), so if that's all you're > using the base class for, you may be able to discard it (o: > > cheers > dim > > On Wed, 31 Oct 2001, Clarance Howatt wrote: > > > I tried to upgrade from version 1.0 to the CVS version of XDoclet > > (downloaded this morning). > > > > I have about 100 EJBeans and all of them inherit from a BasicEntityBean. > > The BasicEntityBean is just a convenience bean so that I do not have to > > define all of the methods defined by the EJB spec. Under 1.0 everything > was > > working great (thanks for making my life so easy). > > > > Now for the bad news, when I try and run the latest version of XDoclet, > I > > get the following error: > > > > [ejbdoclet] (TemplateEngine.invokeMethod 710 ) Invoking method > > failed: p > > arentDataObjectClass , line=9 of template file: > \xdoclet\ejb\dataobject.j > > [ejbdoclet] xdoclet.XDocletException: @ejb:bean class tag expected in > class > > com. > > yottayotta.ejb.BasicEntityBean but not found. > > > > Now I know that all of my entity beans must include the @ejb:bean tag > and > > all of the beans that I wish to run XDoclet with do have this tag. The > > BasicEntityBean does NOT have the @ejb:bean tag but that is by design. > I > do > > not want anything generated based on this file and it has been excluded > in > > the ant build file. And remember, It was working under 1.0. > > > > This behaviour can be reproduced in the samples that come with xdoclet > by > > simple removing the @ejb:bean tag from person.java (make sure you > exclude > > this file in the build.xml file) > > > > Is this a bug or new functionality? > > > > C. > > > > > > > > _______________________________________________ > > 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 _________________________________________________________ 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
