container managed transactions

In the case of J2EE container-managed transactions, the container takes responsibility for determining transaction bounds.

Among these tasks are container-managed transactions, scalability, failover management, and security control.

As you can see, the MDB Bean type is message-driven, and the EJB uses container managed transactions.

Using container-managed transactions is recommended, as the J2EE application server will handle the transaction management.

The bean must set the transaction-type attribute in the EJB deployment descriptor to container to use container-managed transactions.

In short, another best practice is to use container managed transactions wherever possible.

This returns true if the MDB is using container-managed transactions and the method in question has a transaction attribute of Required.

EJBs and container-managed transactions (CMTs) make transaction management virtually transparent to the bean developer.

The stub and skeleton objects also take care of beginning and committing container-managed transactions.

EJB container-managed transactions work even when multiple EJBs collaborate to perform a task.

It's impossible to overemphasize the importance of container-managed transactions.