This week's book giveaway is in the Jobs Discussion forum.
We're giving away four copies of Java Interview Guide and have Anthony DePalma on-line!
See this thread for details.
The moose likes EJB and other Java EE Technologies and the fly likes MDB - Bean Managed Transaction Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Java Interview Guide this week in the Jobs Discussion forum!
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "MDB - Bean Managed Transaction" Watch "MDB - Bean Managed Transaction" New topic

MDB - Bean Managed Transaction

Sub swamy
Ranch Hand

Joined: Oct 02, 2002
Posts: 121
Have an application where MDB's are introduced to implement asynchronous processing. The MDB in-turn is used to call other existing classes which handle the backend interactions. These classes use JDBC transactions - have commit, rollback statements.

This forces me to use Bean Managed Transactions for the MDB. Is there any disadvantage of using BMT over CMT - if so, what needs to be done to address it? Is there any alternative ?
Jaikiran Pai

Joined: Jul 20, 2005
Posts: 10441

Using BMT will force you to take care of the transaction commits/rollbacks etc... (as you can see in the JDBC code that you are mentioning). Other than that i dont see any drawback of using BMT.

Just a question, is there any logic involved in the MDB other than invoking the classes which do JDBC work? If there's no logic involved in the MDB other than this, i dont see a need to have a transaction on this MDB since all the transaction handling will be done by the classes doing JDBC.

[My Blog] [JavaRanch Journal]
Sub swamy
Ranch Hand

Joined: Oct 02, 2002
Posts: 121
The MDB basically delegates task to a set of of handler classes. One among this set of handler does JDBC transaction. Otherwise there is no transaction in MDB.
I agree. Here's the link:
subject: MDB - Bean Managed Transaction
It's not a secret anymore!