Wednesday, February 12, 2003, 4:02:41 PM, you wrote: DW> Brian,
DW> Look at the "Deprecated and Removed" section on this page: DW> http://xdoclet.sourceforge.net/development/design.html . Yes, DW> @use-soft-locking is going to go away (at least in XDoclet 2.0). DW> Now that I think of it, wasn't some version of JBoss (3.2 or 4) going to DW> support Optimistic Locking? Can someone tell me which version? Both already support it. Though, commit option A doesn't make much sense in this case as entity instances are cached per tx, not a global cache. alex DW> Thanks, DW> David DW> (PS: Sorry for the cross-post.) DW> -- DW> Brian Wallis escribi�:: >> XDoclet (1.2b1) generates code for optomistic locking when given the >> use-soft-locking option in @ejb.bean. As is documented, it places the >> increment in the ejbStore() method of the CMP class. >> >> But this doesn't work in JBoss 3 (3.0.4) and probably cannot be guarenteed to >> work in any CMP implementation since (according to the spec) ejbStore() can >> be called at any time and must be called *before* ejbFind<METHOD>(...) calls. >> (section 10.7.4 5th para, 10.5.1 7th bullet, .. and thanks to Dain on the >> Jboss-User list for pointing this out to me). >> >> Perhaps this use-soft-locking option should be deprecated? >> >> brian wallis... >> >> P.S. I'm not sure why it needs to call ejbStore() rather than ejbLoad() but >> that is what the spec says (Version 2.0, 14 August 2001) ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
