--- John Latham <[EMAIL PROTECTED]> wrote:
> How do you document your mapping design? E.g. I have > cascade-delete-orphan on a parent, and then parent > key not-null="false" on the child, so that the child > can be de-linked from the parent in order to be > orphaned (and deleted by Hibernate). I want to be > able to explain this in my source code. If I use > normal javadoc, then my generated API documentation > will contain all this hibernate implementation > garbage. With a @hibernate.... tag I can suppress it > fron appearing in my generated javadoc. I personally prefer explanations in javadoc.... > When I come to debug my system, I look at the > hibernate mapping files first, not the XDoclet > comments. If I see something wrong, I then work out > what needs to change in the mapping file, then how > to realize it using XDoclet comments. So you propose @hibernate.comment once per propery to generate comment? This change would not require a lot of work, and neither it is high priority. Please file JIRA issue so we are remembered about your wish, or even better submit a patch :) regards, ----[ Konstantin Pribluda http://www.pribluda.de ]---------------- Still using XDoclet 1.x? XDoclet 2 is released and of production quality. check it out: http://xdoclet.codehaus.org ____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ xdoclet-plugins-interest mailing list xdoclet-plugins-interest@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xdoclet-plugins-interest
