In the JBoss world when stateful beans are passivated it appears that the JBoss persistent manager is automatically saving the conversational state for me. Based on some tests that I ran, the ejbPassivate() method gets called and then the corresponding ejbActivate(). I was under the impressing that I as a bean developer had to manually save the conversational state via when ejbPassivate() is called, but for JBoss it appears it automatically saves conversational state.
Is this true or are my tests not accurate.
I did notice the ejbPassivate() method being called.
The container passivates/activates the state
based on the cache configuration.
The ejb* methods are so you can release/re-obtain
resources that are not part of the state.
This is not JBoss specific.