[ https://issues.apache.org/jira/browse/OWB-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503277#comment-14503277 ]
Mark Struberg commented on OWB-1048: ------------------------------------ Map in the Session is actually the only approach which works: *) it has the least performance impact *) it doesn't trigger tons of servlet flashbacks and attribute events *) it works with full session rep *) it works with partial session replications if we just re-add the attribute once at the end of the request *) It works fine with parallel request on the same session, as we can manually lock. This is not possible for pure session attributes. So +1 for Thomas' approach. > 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)