Yup, that's another story ;) Fact is: after a session got persisted and deserialised into memory again after the reboot, @SessionScoped and @ConversationScoped beans should imho also get restored.
Problem is: we probably have to re-wire the @ApplicationScoped and other resources in this case :/ Are we really sure that we like to support this for now? Or am I thinking too complicated? Anyway, the changes I did in the API are necessary to be compatible with the Spec! LieGrue, strub --- Gurkan Erdogdu <gurkanerdo...@yahoo.com> schrieb am Fr, 13.3.2009: > Von: Gurkan Erdogdu <gurkanerdo...@yahoo.com> > Betreff: Re: [jira] Created: (OWB-83) allow passivation of scopes > @SessionScoped and @ConversationScoped > An: openwebbeans-dev@incubator.apache.org > Datum: Freitag, 13. März 2009, 15:20 > Currently we are not using the > SevletContainer session object to hold our webbeans > instances. > > When will we passivate and activate the instances ? How > will we decide it? Could we use the servlet container > activation listeners? > > /Gurkan > > > > > > ________________________________ > From: Mark Struberg (JIRA) <j...@apache.org> > To: gurkanerdo...@yahoo.com > Sent: Friday, March 13, 2009 9:47:50 AM > Subject: [jira] Created: (OWB-83) allow passivation of > scopes @SessionScoped and @ConversationScoped > > allow passivation of scopes @SessionScoped and > @ConversationScoped > ------------------------------------------------------------------ > > > Key: OWB-83 > > URL: https://issues.apache.org/jira/browse/OWB-83 > > Project: OpenWebBeans > Issue Type: Bug > Reporter: Mark > Struberg > Assignee: Gurkan > Erdogdu > > > Since sessions of a ServletContainer may be serialised and > persisted to disk on shutdown, SessionScoped and > ConversationScoped context may be passivated >
