Andrew Stevens wrote:
I notice in hibernate-set.xdt it has<XDtMethod:ifHasMethodTag tagName="hibernate.set" paramName="order-by"> <XDtConfig:ifConfigParamEquals paramName="version" value="1.1"> readonly="<XDtMethod:methodTagValue tagName="hibernate.set" paramName="readonly" values="true,false" default="false"/>" </XDtConfig:ifConfigParamEquals> order-by="<XDtMethod:methodTagValue tagName="hibernate.set" paramName="order-by" />" </XDtMethod:ifHasMethodTag> Is that right? Does the readonly attribute only apply if order-by has also been used? Or are they independent?
I believe that attribute has been dropped in Hibernate 2.0+, so the config restriction is valid, but I don't really know what the proper usage is for that attribute in Hibernate 1.1. I just preserved the original condition that was in the hibernate-collections.xdt template...someone with more historical knowledge than I would have to answer that question.
------------------------------------------------------- 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-devel mailing list xdoclet-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
