On 2003.02.11 22:01 Brian Wallis wrote: > > 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)
1. Otherwise you need a in-memeory query engine to find out if any of the in-memory copies of entities satisfy or don't satisfy the query conditions, differently from the db's copy. 2. What if there's a trigger and updating one row deleted lots of others in the db... you need to do the update so the trigger can fire before you do the find and retrieve all the rows that (should have) got deleted. david jencks > > > > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld > http://www.vasoftware.com > _______________________________________________ > xdoclet-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/xdoclet-user > > ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
