First, JDBCOptimisticLock class is deprecated. Just use NoLock and optimistic locking config in jbosscmp-jdbc.xml
You could perform the work that might be rolled back due to optimistic locking failure in a method with RequiresNew transaction attribute, catch the exception in the method that called the method with RequiresNew and react appropriatly. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3841989#3841989 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3841989 ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
