OWB stores @SessionScoped beans in an in-memory map of SessionContext's that is keyed off the session id.
I believe the FailOverService will later store those SessionContext's as a session attribute in the session as part of the FailOverBagWrapper at the end of each request. It should then serialize/restore as appropriate when the session is serialized. Sincerely, Joe On Wed, Feb 16, 2011 at 11:03 AM, Thomas Andraschko <[email protected]>wrote: > Hi, > > I successfully use Tomcat + Memcached Session Manager to replicate my > session and JSF @SessionScoped beans. > Now i tried to use OWB + Memcached SessionManager and it does not working. > > So my questions are: > How OWB stores CDI @SessionScoped beans in a Web/JSF app? > Can a OWB application be clustered? > > Thanks! > > >
