Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

how to check transaction already started or not

 
james edwin
Ranch Hand
Posts: 393
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
hi,

Is it possible to check in CMP any bean (session,entity) that transaction is already started by client(or in previous bean method,like if BEAN B method is called by BEAN A method) or not ?

Regards,

James
 
Roger Chung-Wee
Ranch Hand
Posts: 1683
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
This scenario can only apply for a CMT bean (because a BMT bean will always create its own transaction).

There is no isRunningInCurrentTransaction() method, but you can nevertheless get some some information.

If the transaction attribute is Mandatory and the method is called without an existing transaction context, the Container must throw javax.transaction.TransactionRequiredException to a remote client or javax.ejb.TransactionRequiredLocalException to a local client.

If the transaction attribute is Never and the method is called with an existing transaction context, the Container must throw java.rmi.RemoteException to a remote client or javax.ejb.EJBException to a local client.
 
C Chavan
Greenhorn
Posts: 27
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
In CMT bean, the txn attribute is specified in DD and container manages txn for bean. one can check whether current txn is destined for rollback by calling boolean ejbcontext.getRollbackOnly(). there is no method to my knowledge that will tell whether there is any txn context available. you have to trust container on that

for BMT bean (session only), one can use ut.getStatus() to find out the txn status. note that, BMT bean does not allow txn to propogate in i.e. the client can not pass it's txn to BMT bean.
 
Roger Chung-Wee
Ranch Hand
Posts: 1683
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
A further thought. For a CMT bean, when you are in the middle of a method, you will always know the following (based upon its transaction attribute).

Called with an existing transaction context
===========================================
Mandatory

Possibly called with an existing transaction context
====================================================
Required, Supported

The other attributes (RequiresNew, NotSupported and Never) will never run in an existing transaction context.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic