How I would probably try to solve this - and I have not had time to really sit down and think it through fully - is to have an interceptor wrapped around my EJB that knows how to catch the exception and forward to the appropriate recovery mechanism. This is always either:
(1) A page that tells the user "someone else updated this, go back to the start and try again" (2) A page that tells that user "heres the data that you entered, heres the current data in the database, you need to merge those changes together" - and then this work needs to be done in a new PC and txn. To "get" a new PC/txn to work with, call a session bean in the context of a REQUIRES_NEW transaction (if it is stateful, it needs to be a newly instantiated SFSB). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3919517#3919517 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3919517 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
