Get the tools you need to learn Java skills fast!
Video tutorials, eBooks, hands-on lab exercises, sample code.
Get started
The moose likes EJB Certification (SCBCD/OCPJBCD) and the fly likes Unspecified transaction context Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Badass: Making Users Awesome this week in the Game Development forum!
JavaRanch » Java Forums » Certification » EJB Certification (SCBCD/OCPJBCD)
Bookmark "Unspecified transaction context" Watch "Unspecified transaction context" New topic

Unspecified transaction context

Balaji Anand
Ranch Hand

Joined: Nov 03, 2004
Posts: 146

page 499 of HFEJB says ejbCreate() ejbRemove() ejbActivate() and ejbPassivate() of the CMT Session Bean are in unspecified transaction context(the container can choose to do what ever it wants including no tran,merging multiple calls to one)

But 7.5.7 of the spec adds newInstance, setSessionContext and afterCompletion methods to this.

I was thinking that these runs with 'No Transaction Context" always?
Is this left in the book?can someone help

[ March 15, 2006: Message edited by: Srividhya Anand ]
Saeed Amer
Ranch Hand

Joined: Jan 20, 2004
Posts: 140
Maybe "Unspecified Transaction Context" and "No Transaction Context" mean the same thing?
Balaji Anand
Ranch Hand

Joined: Nov 03, 2004
Posts: 146
I am not sure if it means the same...

"unspecified tran context" from the spec

� The Container may execute the method and access the underlying resource managers without a transaction context.
� The Container may treat each call of an instance to a resource manager as a single transaction (e.g. the Container may set the auto-commit option on a JDBC connection).
� The Container may merge multiple calls of an instance to a resource manager into a single transaction.
� The Container may merge multiple calls of an instance to multiple resource managers into a single transaction.
� If an instance invokes methods on other enterprise beans, and the invoked methods are also designated to run with an unspecified transaction context, the Container may merge the resource manager calls from the multiple instances into a single transaction.
� Any combination of the above.

"Without a transaction" is only a case in unspecified transaction context
I agree. Here's the link:
subject: Unspecified transaction context