• 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
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

BMT & CMT in ejbCreate

 
Ranch Hand
Posts: 122
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi All,

I have a significant point to get clarified. In case of stateful session bean, we will not be able to call methods on the (BMT) user transaction object, inside setSessionContext. Why is this? But, we will be able to do the same thing in the business method. What determines the access to the transaction method access? Also, how is this different incase of CMT based methods(setRollbackOnly & getRollbackOnly).

Thanks:
 
Ranch Hand
Posts: 222
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

In case of stateful session bean, we will not be able to call methods on the (BMT) user transaction object, inside setSessionContext. Why is this?



That's because setSessionContext runs under unspecified transaction context. Look at this page on Frederic's site. This table summarizes the various methods of various beans and their transaction context association. The spec page numbers, from where these details are taken, are also mentioned on the table.
reply
    Bookmark Topic Watch Topic
  • New Topic