bean-managed-transactions

This scenario using CMT is working: Stateless session bean with CMT, one method annotated with @TransactionAttribute(TransactionAttributeType.MANDATORY) . Within this method, a record is written into a RDBMS using an XA data source and plain JDBC. The stand-alone client (separate JVM, command-line Java application) is getting a UserTransaction from the application server (by JNDI lookup), starts the transaction, and calls the EJB. If the client commits the UserTransaction , the record is written into the database. If the client rollbacks the UserTransaction , the record is not written into the

A quote from the EJB 3.1 specification : 13.6.1 Bean-Managed Transaction Demarcation The container must manage client invocations to an enterprise bean instance with bean-managed transaction demarcation as follows. When a client invokes a business method via one of the enterprise bean’s client views, the container suspends any transaction that may be associated with the client request. On the other hand, a transaction from a stand-alone client or another EJB is propagated into a bean using container-managed transactions . Looking at it from the CMT perspective, it seems that beans using CMT

I have a stateless bean with bean-managed transactions, and a method like this: @Stateless @TransactionManagement(TransactionManagementType.BEAN) public class ... { @Resource private UserTransaction ut; @EJB private OtherStatelessBeanLocal other; public void invokeSomeMethods() ut.begin(); ... // invoke other bean's methods here. other.method(); ... ut.commit(); } } So how does the UserTransaction propagate to the OtherStatelessBeanLocal bean? The UserTransaction object is an object supplied by the container which wraps access to API calls that the container uses internally, specifically javax