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

Antonio Goncalves (JIRA) issues at jboss.org
Sat Sep 26 10:57:00 EDT 2015

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

Antonio Goncalves commented on CDI-383:

In Servlet 3.1 spec §11.3.4 Notifications At Shutdown

On application shutdown, listeners are notified in reverse order to their declarations with notifications to session listeners preceding notifications to context listeners. Session listeners must be notified of session invalidations prior to context listeners being notified of application shutdown.

> 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