"[EMAIL PROTECTED]" wrote : | wHAT DO OTHER PEOPLE THINK ? Well, Bela, now there's no reason to shout! :)
DashV, makes sense. With optimistic locking, we first check for an existing transaction, and if there isn't one, we implicitly start one. Before the method returns, if we started the tx ourselves, we make sure we commit it. So perhaps there is scope to 'replay' the tx a fixed number of times here if it were to throw a RollbackException on commit. Bela, I don't think this leads to very different semantics - at the moment, if the developer explicitly starts a tx before any cache operations, the cache may throw a RollbackException if it is unable to commit. If the developer doesn't explicitly start a tx, the cache may fail silently if it is unable to commit, logging errors but not throwing any exceptions. So there is scope here for silent retries. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3903734#3903734 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3903734 ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
