[
https://issues.apache.org/jira/browse/OWB-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503303#comment-14503303
]
Romain Manni-Bucau commented on OWB-1048:
-----------------------------------------
@mark: this is the issue, it should be the session which matches this map, not
an attribute. Also ConcurrentHashMap doesn't solve the distribution case which
is mainly the one we need to ensure to be compliant with. Keep in mind session
distribution can be async, with ack or not etc...(all these case in just tomcat
can happen). That is why using session *by default* can be an issue and a
regression compared to previous impl.
> Store @SessionScoped beans in real HttpSession if available
> -----------------------------------------------------------
>
> Key: OWB-1048
> URL: https://issues.apache.org/jira/browse/OWB-1048
> Project: OpenWebBeans
> Issue Type: Improvement
> Components: Context and Scopes
> Affects Versions: 1.5.0
> Reporter: Mark Struberg
> Fix For: 1.5.1
>
>
> Currently we always store our @SessionScoped beans in a Map<String sessionId,
> Map<beanbags>> in memory.
> This causes some nasty issues with sessionId rewrites. We also need the
> pretty complicated FailOver handling for enabling sane cluster behaviour.
> We do not need any of those things if we utilize the real HttpSession IF
> available. That means we do still use a mem-backed Map for owb-core, but
> provide a different SessionContext impl in the owb-web module.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
