So, your ENFE exception is propagated to the nester of the EJB? If a runtime exception gets thrown pass an EJB boundary then the transaction is marked for rollback.
You can't get around this. Refactor your code to use find() and check for NULL or catch the ENFE exception within the nested EJB call and wrap it with a non-rollbacking exception (checked or runtime annotatied with @ApplicationException(rollback=false)), or, just change the contract of your nested EJB invocation. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3914488#3914488 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3914488 ------------------------------------------------------- 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
