This week's book giveaway is in the JDBC and Relational Databases forum.
We're giving away four copies of Murach's MySQL and have Joel Murach on-line!
See this thread for details.
Win a copy of Murach's MySQL this week in the JDBC and Relational Databases forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Message Driven Beans and Transactions

 
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,
I posted this question earlier, but haven't gotten a response to it yet :
---------------
Hi all,
The EJB 2.0 spec says that Message Driven Beans (MDB) are only allowed a transactional attribute of either Required or NotSupported. The reasons it gives for this is as follows :
1) Since a MDB never gets called by a client so to speak, there is never a pre-existing transactional context, hence, RequiresNew and Supports, both which deal with client transactions, are meaningless to MDBs
2) Also, since Mandatory and Never throw exceptions to clients if the methods are executed in a transaction, and since there is never an MDB client, these 2 are also meaningless.
Now, I understand these 2 points totally. But in the same vein, why allow Required and NotSupported ??? Required also deals with client transactions (if one exists, Required means container will execute the transaction under the client transaction) and NotSupported suspends a client transaction (if one exists)...and since a MDB never has a client, these 2 also should be meaningless in the context of a MDB. So why allow these 2 but not the rest ??
I know that the container, according to the specs, creates a new transaction everytime for a MDB as it has no client, but I do not understand why it allows Requires and NotSupported, but not the others ???
Any ideas ??
--------------
If anyone knows the answer to this, please let me know.
Regards,
Suman
 
mister krabs
Posts: 13974
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Here's the deal... NotSupported indicates that the message will be processed without a transaction. Required indicates that the message will be processed with a container-initiated transaction.
 
Suman Chaudhuri
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thomas, you wrote :
Here's the deal... NotSupported indicates that the message will be processed without a transaction. Required indicates that the message will be processed with a container-initiated transaction.
I understand what NotSupported and Required are meant to do...but NotSupported also states that if there is a client transaction, then it will suspend it...and since there is no client in a MDB, this is meaningless. Same with Required..which states that if there is a client transaction, it will execute under it (otherwise initiate its own transaction)...again, no client makes this meaningless too.
So I still dont understand why these 2 can apply to MDB.
 
Thomas Paul
mister krabs
Posts: 13974
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Since there is no client, that part of the description obviously doesn't apply. The only question is will the container create a transaction to run the MDB or not.
 
reply
    Bookmark Topic Watch Topic
  • New Topic