• Post Reply Bookmark Topic Watch Topic
  • New Topic

Query - SessionSynchronization interface

 
Ashwin Jahagirdar
Greenhorn
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 ?
 
TeGo Gokhale
Greenhorn
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.
 
Gravity is a harsh mistress. But this tiny ad is pretty easy to deal with:
the new thread boost feature: great for the advertiser and smooth for the coderanch user
https://coderanch.com/t/674455/Thread-Boost-feature
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!