As you can see (or not see if you skipped it), XDoclet generates the
properties for the interface, which is correct, as well as for the
subclass, which is incorrect. The Hibernate templates explicitly
state that superclasses shouldn't be checked, which also implies that
implemented interfaces shouldn't be checked for @hibernate tags.
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 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.)
Paul
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ xdoclet-devel mailing list xdoclet-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
