This problem can be solved by specyfing 'RequiresNew' on all the methods of the Entity bean in question. I'm using the pattern from Floyd's book, and setting the transaction attribute like the following solved the problem:
| <container-transaction> | <method> | <ejb-name>SequenceEJB</ejb-name> | <method-name>*</method-name> | </method> | <trans-attribute>RequiresNew</trans-attribute> | </container-transaction> | <container-transaction> | <method> | <ejb-name>SequenceSessionEJB</ejb-name> | <method-name>*</method-name> | </method> | <trans-attribute>Required</trans-attribute> | </container-transaction> | <a href="http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3825929#3825929";>View the original post</a> <a href="http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3825929>Reply to the post</a> ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
