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
