• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

stateful CMT, calls from ejbCreate

 
David Crecente
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi all,
I have failed a question on http://jdiscuss.com/ that I don't understand after seeing the specification.

According to the specification, in a stateful session bean CMT, on its ejbCreate method, I could have access to other enterprise bean (page 80). But, according to the page 76, ejbCreate runs with an unspecified transaction.

If I can't protect these calls defining a transaction attribute from this ejbCreate, why can I perform methos on other enterprise beans?

Thank you in advance.

Page 80 allowed operations stateful session bean CMT

ejbCreate
ejbRemove
ejbActivate
ejbPassivate
SessionContext methods: getEJBHome,
getEJBLocalHome, getCallerPrincipal,
isCallerInRole, getEJBObject,
getEJBLocalObject
JNDI access to java:comp/env
Resource manager access
Enterprise bean access


Page 76

A session bean�s newInstance, setSessionContext, ejbCreate, ejbRemove, ejbPassivate,
ejbActivate, and afterCompletion methods are called with an unspecified transaction
context. Refer to Subsection 17.6.5 for how the Container executes methods with an unspecified
transaction context.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic