> > "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?
I think after seeing all these negative reactions to the automatic inheritance of home/pk I can conclude that we should remove inheritance. PK inheritance is actually very tricky and mostly you should use a single class for the whole hierarchy. Home inheritance is ok, put common collection-based finders there or finders which return base types. But seems like people like to use the flat model more, so +1 to removing the auto-inheriting. Ara. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
