[
https://issues.apache.org/jira/browse/OWB-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503284#comment-14503284
]
Romain Manni-Bucau commented on OWB-1048:
-----------------------------------------
@Mark: if you put the whole map in the session you'll kill the server regarding
performance if you have several instances + you'll kill consistency as well
(from owb we can't do anything). Not sure it is a good default at all.
That said with all the discussion it seems it triggers we should push it on the
list before working on it no?
> 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)
