Hello Eric;
Currently we have no support for those callbacks for managed beans. Also
includes AroundTimeout method.
Motivation
----------------------
Actually we have 2 methods in WebBeansConfigurationListener. Currently our
session and conversation context does not provided actiovation/passivation.
What we have to do is that we update below lifecycle callbacks to put all
session and conversation context instances into the session in the
"sessionWillPassivate" and call passivate callback, and reverse it on
"sessionDidActivate".
Those areas needs some contributions :)
/**
* {...@inheritdoc}
*/
@Override
public void sessionDidActivate(HttpSessionEvent event)
{
//TODO activation
//Gets all passivated instances from passivated session and restore our
session and conversation context.
}
/**
* {...@inheritdoc}
*/
@Override
public void sessionWillPassivate(HttpSessionEvent event)
{
//TODO Passivation
//Gets all instances from the Session and ConversationContexts
and add those into the session that is under passivation therefore our
bean instances
are correctly passivated
}
Thanks;
--Gurkan
________________________________
From: Eric Covener <[email protected]>
To: [email protected]
Sent: Wed, May 26, 2010 6:29:41 PM
Subject: pre_passivate/post_activate lifecycle callbacks
I see some of this related code is commented out in InterceptorUtil --
what's the background here?
--
Eric Covener
[email protected]
