Just as a note, I finally did figure this one out. Turns out that the problem lies within my ejb-jar.xml for these beans. I had <transaction-type> set to Bean when it should have been Container. Much thanks, and apologies, to those who tried to help here. Hopefully this helps someone else in the same situation. Just as a note, does jboss have a tool to verify ejb jar files? I found this problem using weblogics tool weblogic.ejbc on the file.
Regards and humbly Eric > -----Original Message----- > From: Eric Kaplan [mailto:[EMAIL PROTECTED]] > Sent: Friday, January 18, 2002 12:12 PM > To: [EMAIL PROTECTED] > Subject: BMP Transactions > > Hi > > Does anyone have experience with bean managed persistence in transactions. > In my case, I have a stateless session bean which modified two BMP entity > beans. Upon modification of the second entity bean, a failure should > result in rollback of the entire uncommitted transaction. I'm finding > this is not happening, and the server is printing out TRANSACTION ROLLBACK > EXCEPTION along with the original system error. I have tried both > declarative transaction management and explicit (begin, commit, rollback) > and neither seems to work. I should mention, I have an example of a > stateful session bean which inserts into two tables and publishes via JMS > all in a transaction spread over several calls to the bean and this does > work properly, so it doesn't seem to be configuration related. > > Any help would be appreciated. Does anyone have experience with BMP and > transactions specifically? > > Thanks > > Eric >
winmail.dat
Description: application/ms-tnef
