Summary

Today you learned how to use, develop, and deploy EJBs with bean-managed transaction demarcation. This type of transaction management is the programmatic approach to controlling transaction boundaries in the application code. Transaction demarcations are embedded into the EJB code, whether you try to commit, roll back, or abort a transaction. BMT is used mainly by advanced users who want to have more control over their transactions. You can use either local or global transactions when developing an EJB with BMT.

According to the EJB architecture, only session and message-driven beans can use bean-managed transactions. Entity beans can use only container-managed transactions. A working example was given to illustrate the use of a session bean (Student EJB) with BMT. You also studied the restrictions imposed by the J2EE architecture on the use of BMT, and the transaction semantics of each EJB method.