DikkeDouwe, Your recommendation of setting the <trans-attribute> to "NotSupported" did solve the problem. However, I don't want transactions to be not supported!
In fact, the "Required" attribute (or "RequiresNew") is exactly what I want, because I want a transaction around the operation of my session bean. However, whenever I try this, it fails with the original error. The other alternative, setting <transaction-type> to be "Bean" also seems like a pretty dumb idea, since the whole aim is to allow my XA transactions to be managed by the container, rather than me having to manage them myself! Why shouldn't I be able to run a container-managed transaction within JBoss using Oracle as an XA resource? Have I got the wrong end of the stick here or something?!? <a href="http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3827113#3827113";>View the original post</a> <a href="http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3827113>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
