HttpSessionListener.sessionCreated should be called in order listener was added; sessionDestroyed in reverse order #4752
Labels
TCK
For various Specification Test Compatibility Kits (eg: Servlet, WebSocket, HTTP/2, etc)
Jetty calls all HttpSessionListener methods in reverse order that the listener was added. According to the javax.servlet.http.HttpSessionListener javadoc, sessionCreated() must be invoked in the order the listener was added, but sessionDestroyed() must be called in reverse order.
See https://github.com/eclipse-ee4j/jakartaee-tck/blob/master/src/com/sun/ts/tests/servlet/api/javax_servlet_http/servletcontext304/URLClient.java
The text was updated successfully, but these errors were encountered: