Shouldn't this be a specfic exception class as in OptimisticConcurrencyViolation or something to that effect. The generic throwing of EJBException with a message detailing the violation makes this more difficult to handle (Parse message for key words "Row was Updated"????) . Most exception get packed up and sent back to the client with some vague message about contacting support... but this error can actually be handled gracefully.
Am I missing something? Thanks Jim View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3911983#3911983 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3911983 ------------------------------------------------------- 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://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user