The container manages that state so it could be vendor specific as to the exact method they are using to do it. According to the EJB spec, the container cannot retain the state when the session bean instance is passivated. You should read section 7.4 for more details and check your vendor specific docs as well.
A discussion on How and where should session state be maintained is at
http://java.sun.com/blueprints/qanda/app_arch/index.html
In a stateful session bean the client session state is stored by the EJB container. This is described a bit more at
http://java.sun.com/blueprints/qanda/ejb_tier/session_state.html
hope that helps,
Sean
I am new to MVC and encounter similar design issues.
In a redundant network (both application server and web server) how could I pre-serve user session info (eg. user name/password) when application server/web server is down. Will it be product specific ? My client use iPlant as web server and WebSphere as the appl seerver.
Thanks in advance in any comments/remarks
Sargon