it depends how much you feel like contributing (o: for the moment, all you need to do is change the entitycmp.j (or entitybmp.j) file in the xdoclet.jar. Probably the first thing to do is read over the file and get a feel for the templating syntax. Also look at the docs under the template tags section (you should have a copy of the docs with your dist, but they're also online at http://xdoclet.sourceforge.net).
Once you've done that, essentially what you want to do is change the template where it generates the set/get methods, its inside the <XDoclet:forAllPeristentFields> block. *** WARNING *** The templating mechanism is about to change as a result of some refactoring currently going on. For instance, the <XDoclet:forAllPersistentFields> tag will be <XDtEjbPersistent:forAllPersistentFields> once some current refactoring is done. THis is to achieve a cleaner namespace separation. Dont worry about this just yet though, it will be a pretty painless transition. ok - hope thats enough to at least get you started... I'm sure you'll have a heap of questions (o: feel free to ask... cheers dim We're talking cmp entity beans right? On Fri, 19 Oct 2001, Mike Cannon-Brookes wrote: > Sure it does - that's the way I personally would _expect_ it to work? > > Where should I start looking? ;) > > -mike > > > Mike Cannon-Brookes :: [EMAIL PROTECTED] > > Atlassian :: http://www.atlassian.com > Supporting YOUR J2EE World > > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]]On Behalf Of Dmitri > > Colebatch > > Sent: Friday, October 19, 2001 10:48 AM > > To: Mike Cannon-Brookes > > Cc: Ara Abrahamian; [EMAIL PROTECTED] > > Subject: RE: [Xdoclet-user] XDoclet with subclasses - dangerous? > > > > > > On Fri, 19 Oct 2001, Mike Cannon-Brookes wrote: > > > > > > > > How can I tell XDoclet to 'ignore bar in the generation and trust me it > > > already exists'? I want it to churn out code in C like : > > > > > > public Foo getBar() > > > { > > > return super.getBar(); > > > } > > > > > > I have a sneaking suspicion that you're going to tell me it's just not > > > possible - which bites bigtime because it rules a lot of EJBs > > out of being > > > XDoclet generated. > > > > > > > its not possible atm out of the box, but there's no reason why you > > couldn't implement it. If all your ejbs follow this model you could just > > change the template to produce the code you want. Or, you could change > > the template to check to see if super.getBar is not abstract, and call the > > code based on that. THe second approach is something that could become > > part of the project so that others have the benefit too. > > > > does that make sense? > > > > cheesr > > dim > > > > > > _______________________________________________ > > 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 > _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
