This week's book giveaway is in the Raspberry Pi forum.
We're giving away four copies of Getting started with Java on the Raspberry Pi and have Frank DelPorte on-line!
See this thread for details.
Win a copy of Getting started with Java on the Raspberry Pi this week in the Raspberry Pi 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
  • Ron McLeod
  • Paul Clapham
  • Tim Cooke
  • Jeanne Boyarsky
Sheriffs:
  • Rob Spoor
  • Devaka Cooray
  • Liutauras Vilda
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Tim Moores
  • Mikalai Zaikin
Bartenders:
  • Piet Souris

stateful CMT, calls from ejbCreate

 
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • 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.
 
reply
    Bookmark Topic Watch Topic
  • New Topic