Originally posted by Kengkaj Sathianpantarit:
No, SessionSynchonization is for synchronizing purpose, hence stateless session bean don't need to implement it because stateless session bean don't have state.
Ok, I understand that since SessionSynchronization is mainly for synchronizing the state and since the SLSB doesn't maintain any state hence they don't need to implement the SessionSynchronization.
But I am still confusing on why would the SLSB need to manage transaction? Probably what I understand is that, transaction management is only important when the transaction has to span over multiple methods.
Can someone give me a example scenario wherein a problem would occur in case the SLSB is not associated with any transaction?