Win a copy of Svelte and Sapper in Action this week in the 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 all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

Query - SessionSynchronization interface

Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Stateless session beans are not allowed to maintain transactions across multiple methods, so they must not implement SessionSynchronization interface. Does this mean that stateful CMT session bean is able to maintain transactions across multiple methods ? In CMT, transaction attributes are scoped at method level so how is it possible to maintain a transaction across multiple methods ?
Posts: 11
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I think maintaining state and transaction should be looked seperately.
Session synchronizatiion int. gives chance to keep bean synchronized with underlying per. store and key milestones during a transaction. This is important for stateful bean because it has to maintain a state accross method calls.
So ss interface is for synching the bean state accross method calls.

CMT stateful session beans cannot continue transaction accross method calls but still have to be synched with underlying datastore.

Correct me if I am wrong.
snakes are really good at eating slugs. And you wouldn't think it, but so are tiny ads:
Thread Boost feature
    Bookmark Topic Watch Topic
  • New Topic