going this way looks consistent 2 me since default generated code is always useless in that case (and so introduces xtags to add to all EJB classes that use inheritance to redirect inheritance to default javax or other). considering fact that most industries work with framework layered oriented architecture, would be great to consider EJB inheritance. thanx for concern, seb.
Aslak Hellesoy wrote: > > -----Original Message----- > > From: Sebastien BLANC [mailto:Sebastien.Blanc@;alcatel.com] > > Sent: 28. oktober 2002 16:03 > > To: Aslak Hellesoy > > Cc: [EMAIL PROTECTED] > > Subject: Re: [Xdoclet-user] bean inheritance / home generation > > > > > > Hello ! > > "XDoclet should generate a BHome that *does not* extend from AHome" > > currently with samples I get the following generation: > > public interface CustomerHome extends test.interfaces.PersonHome > > does that mean this is a bug in xdoclet ? > > thank you. > > seb. > > > > It's the way it currently works, and expected behaviour. I wouldn't say it's > a bug, because it was designed to work this way. I'm only suggesting it's > bad design, and asking the community if it thinks we should remove > inheritance from home interfaces. > > I think we should. What do you think? > > Aslak > > > Aslak Hellesoy wrote: > > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
