What are the restrictions that apply to a bean-managed transaction?

The restrictions that apply to a bean-managed transaction (BMT) are as follows:

• A BMT does not allow nested transactions. This means a BMT must complete the current transaction before starting a new one. Completing the current transaction means it should either be committed or rolled back.
• For a stateless session bean and a message-driven bean, a method cannot complete before completing a transaction. However, for a stateful session bean, a transaction may not be complete when a method completes.
• Only session beans and message-driven beans can use a bean-managed transaction. An entity bean can never use a bean-managed transaction.
• A BMT transaction can never run within another bean’s transaction. This means that a BMT should necessarily have its own transaction. BMT beans will never use an incoming transaction context from a caller. If another bean’s method calls a method from a BMT, the calling bean’s transaction will be suspended.

• Download free practice test for ciw-professional CIW Professional exam.
• Get certified in first attempt download master-ciw-enterprise-developer - Master CIW Enterprise Developer simulation.
• Click here to get free scbcd SCBCD exam practice questions.
• Download practice question and study guide for 1D0-442 for exam.
• Best exam simulation SUN CX310-090 download free trial.
• Click here to download CX310-091 test study guide and practice question.
• Pass SUN CX310-092 - SCBCD Java Upgrade

• Previous Entry: What is the RequiresNew transaction attribute?
• Next Entry: EJB programming restrictions