[
https://jira.jboss.org/jira/browse/WELD-403?page=com.atlassian.jira.plugi...
]
Nicklas Karlsson commented on WELD-403:
---------------------------------------
As we discussed, it could be an idea to have a sort of delegating
"PassthroughBeanStore" which extends the session based BeanStore and has a local
ConcurrentHashMapBeanStore which keeps a local copy.
You could then have a reload() function that would re-populate the session backed
BeanStore from the local one. This could be called in a session-terminated listener after
the session BeanStore would have been re-activated with a fresh session from
request.getSession(true). This would work out from a clustering-point-of-view and
wouldn't leave us hanging if the user invalidates the session. There would be some
duplication but the operations are fast...
Activate session scope after call to HttpSession.invalidate()
-------------------------------------------------------------
Key: WELD-403
URL:
https://jira.jboss.org/jira/browse/WELD-403
Project: Weld
Issue Type: Feature Request
Components: Scopes & Contexts
Affects Versions: 1.0.0.GA
Reporter: steven verborgh
Assignee: David Allen
Fix For: 1.0.1.CR2
Attachments: session_invalidate.tar.bz2
When calling HttpSession.invalidate() and redirecting to a page that uses a SessionScoped
Bean a ContextNotActiveException exception gets thrown.
This is a different behavior than when using the optional JSF annotations (ManagedBean,
SessionScoped) and is also different from the standard HttpRequest behaviour where a call
HttpRequest.getSession() by default creates a new Session, even after a call to invalidate
in the same request/response cycle.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira