You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@openwebbeans.apache.org by "Gurkan Erdogdu (JIRA)" <ji...@apache.org> on 2010/06/02 21:00:52 UTC

[jira] Updated: (OWB-338) our internal SessionContext and ConversationContext must support Session serialization

     [ https://issues.apache.org/jira/browse/OWB-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gurkan Erdogdu updated OWB-338:
-------------------------------

        Fix Version/s: 1.0.0-CR2
                           (was: 1.0.0-CR1)
    Affects Version/s: 1.0.0-CR1
                           (was: M4)

> our internal SessionContext and ConversationContext must support Session serialization
> --------------------------------------------------------------------------------------
>
>                 Key: OWB-338
>                 URL: https://issues.apache.org/jira/browse/OWB-338
>             Project: OpenWebBeans
>          Issue Type: Bug
>          Components: Context and Scopes
>    Affects Versions: 1.0.0-CR1
>            Reporter: Mark Struberg
>             Fix For: 1.0.0-CR2
>
>
> Currently we do not store @SessionScoped and @ConversationScoped beans in the session. Thus if the session gets serialized (e.g. in a cluster scenario or on server restart), we loose all those contextual instances.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.