[cdi-dev] [JBoss JIRA] (CDI-383) Clarify that session context is also destroyed at shutdown/undeploy

Martin Kouba (JIRA) issues at jboss.org
Thu Sep 17 08:01:00 EDT 2015

    [ https://issues.jboss.org/browse/CDI-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13109929#comment-13109929 ] 

Martin Kouba commented on CDI-383:

Well, an HTTP session does not have to be destroyed after a container is shut down. This is not defined in the servlet spec and I did not find anything relevant in the Java EE spec. See also CDITCK-482 comments. However, if we redefine this and state that it's destroyed after an HTTP session is invalidated, we would probably break backward compatibility (see also CDI-497).

> Clarify that session context is also destroyed at shutdown/undeploy
> -------------------------------------------------------------------
>                 Key: CDI-383
>                 URL: https://issues.jboss.org/browse/CDI-383
>             Project: CDI Specification Issues
>          Issue Type: Bug
>          Components: Contexts
>    Affects Versions: 1.1.PFD
>            Reporter: Marko Lukša
> Section 6.7.2. states "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."
> The first part of the above sentence should not only say that the context is destroyed after all listeners have been called specifically in the event of a session timeout. It should specify that this is also true when the session is being destroyed as a result of server shutdown or web-app undeploy.

This message was sent by Atlassian JIRA

More information about the cdi-dev mailing list