> Well I suppose an interesting question is: what do you expect to happen > when a subclass implements an interface (which has @hibernate tags) that > is not the primary interface that your hibernate mapping is designed for?
I'm expecting that the subclass tags won't have any property tags since they're inherited from the top level class. (Hibernate doesn't know or care that it's an interface.) If all of the tags in the interface showed up in the subclass, that would be one thing. However, only the property tags are there. > I hate it when people suggest I do something other than what I want to > do...but that's what I'm going to to you :-). Why not just put your > @hibernate tags on the implementation class and remove them entirely > from the interface? (And simply create a mapping for the implementation > class.) I agree with you. But at the risk of sounding unreasonable, the module should support this properly. ------------------------------------------------------- SF.Net email is sponsored by: Tell us your software development plans! Take this survey and enter to win a one-year sub to SourceForge.net Plus IDC's 2005 look-ahead and a copy of this survey Click here to start! http://www.idcswdc.com/cgi-bin/survey?id5hix _______________________________________________ xdoclet-devel mailing list xdoclet-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
