Win a copy of React Cookbook: Recipes for Mastering the React Framework this week in the HTML Pages with CSS and JavaScript 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 ...
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Rob Spoor
  • Liutauras Vilda
  • Jeanne Boyarsky
  • Junilu Lacar
  • Tim Cooke
Saloon Keepers:
  • Tim Holloway
  • Piet Souris
  • Stephan van Hulst
  • Tim Moores
  • Carey Brown
  • Frits Walraven
  • Himai Minh

Stateless/stateful beans and lifecycle

Ranch Hand
Posts: 244
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have a doubt about page 79 specs: for stateful session beans, you can access to enterprise beans at lifecycle callback methods. However, this is not true for stateless session beans. The specs say that this is due to the fact that there is not transaction context (pag. 90), but at paragraph 13.6.5, the specs say that "The execution of a PostConstruct, [...], PrePassivate callback method of a session bean with container-managed transaction demarcation" are executed in an unspecified transaction context.
So, why can a stateful session bean invoke, for example, an enterprise bean, in a lifecycle callback interceptor method even if there is not transaction context?

Thanks in advances
Space pants. Tiny ad:
the value of filler advertising in 2021
    Bookmark Topic Watch Topic
  • New Topic