[
https://issues.apache.org/jira/browse/OWB-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved OWB-1050.
--------------------------------
Resolution: Fixed
Fix Version/s: (was: 1.5.1)
1.6.0
> Store the Map<conversationId, conversationContexts> in the SessionContext
> --------------------------------------------------------------------------
>
> Key: OWB-1050
> URL: https://issues.apache.org/jira/browse/OWB-1050
> Project: OpenWebBeans
> Issue Type: Improvement
> Components: Context and Scopes
> Affects Versions: 1.5.0
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> Fix For: 1.6.0
>
>
> Currently we store the ConversationContext in a mem-backed map.
> But this requires all sort of weird handling at cleanup and for cluster
> support.
> If we store the ConversationContext in the SessionContext instead then we do
> not need all this anymore.
> We also probably could get rid of the ConversationManager which heavily
> relies on the sessionId as well.
> ATTENTION: The implementation of the ConversationContext must not eagerly
> create HttpSessions but only if a @ConversationScoped contextual instance
> gets requested! Otherwise we will trash the server with creating a fresh
> session for SOAP requests, REST calls and other resource requests.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
