Explain Bean-managed Transaction?

1.	Explain Bean-managed Transaction?
Answer» When an enterprise bean defines the boundaries of the transaction it is referred as bean-managed transaction. In bean-managed transaction demarcation, the code in the session or message-driven bean explicitly MARKS the boundaries of the transaction. Although beans with container-managed transactions require less CODING, they have one limitation: When a method is executing, it can be associated with either a single transaction or no transaction at all. If we use bean managed transaction we are responsible for programming transaction logic into your application code so that developers are responsible for issuing a 'begin' statement and either a 'commit' or an 'abort' statement. The benefit of bean managed transaction is that as a DEVELOPER you have full control over TRANSACTIONAL boundaries. For instance, you can run series of mini transactions WITHIN a bean's method using bean managed transaction.

Answer»

When an enterprise bean defines the boundaries of the transaction it is referred as bean-managed transaction. In bean-managed transaction demarcation, the code in the session or message-driven bean explicitly MARKS the boundaries of the transaction.
Although beans with container-managed transactions require less CODING, they have one limitation: When a method is executing, it can be associated with either a single transaction or no transaction at all. If we use bean managed transaction we are responsible for programming transaction logic into your application code so that developers are responsible for issuing a 'begin' statement and either a 'commit' or an 'abort' statement.
The benefit of bean managed transaction is that as a DEVELOPER you have full control over TRANSACTIONAL boundaries. For instance, you can run series of mini transactions WITHIN a bean's method using bean managed transaction.

Discussion