Assume i have a bean class with CMT. And i am calling methodA in the bean which starts out a transaction(having Required/Required_new attribures).This is followed by the subsequent calls to the other methods of the bean class which are all having their own transaction attributes that might let the bean to continue with the existing transaction context,else to start a new one, or even to destroy the existing.
my doubt is,
1. when the container does the commit for the existing transaction started by the first method.
2.In core specs page no 360, first case under container's action why there is no info about calling setRollbackOnly().Is it not possible to set the transaction to rollback when it's the one from the caller's
when you really want something, all the universe always conspires in your favour.<br /> <br />SCJP1.5-77%<br />SCWCD-89%
first case under container's action why there is no info about calling setRollbackOnly().Is it not possible to set the transaction to rollback when it's the one from the caller's
The first action that container will take is to propagate back the exception (along with marking Tx for rollback if needed) . Since the transaction was initiated by the client. It is the client which will rollback after checking for status and knowing if setRollback was invoked by another bean that took part in Tx.
So - the one who starts it : in that bean there is a check for the status and rolling back if needed.
/** Code speaks louder than words */
For my next trick, I'll need the help of a tiny ad ...
Free, earth friendly heat - from the CodeRanch trailboss