[
https://issues.jboss.org/browse/CDI-497?page=com.atlassian.jira.plugin.sy...
]
Antoine Sabot-Durand commented on CDI-497:
------------------------------------------
Form what I understand your concern is with [6.7.2. Session context
lifecycle|http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#session_context]
{quote}
The session context is destroyed when the {{HTTPSession}} times out, after all
{{HttpSessionListener}} s have been called, and at the very end of any request in which
{{invalidate()}} was called, after all filters and ServletRequestListener s have been
called.
{quote}
You'd like to see the session scope destroyed when {{invalidate}} is called not at the
end of the request as it's specified now?
session scope doesn't follow session lifecycle
----------------------------------------------
Key: CDI-497
URL:
https://issues.jboss.org/browse/CDI-497
Project: CDI Specification Issues
Issue Type: Feature Request
Reporter: Romain Manni-Bucau
ATM session destroyed event is bound to the request. this means a logout will not be able
to access the right session when destroyed since most of the time logout = session
destruction and then you can recreate a session (login case).
Would be great to align CDI scopes - and then events - to the real lifecycle of the
underlying observed event.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)