DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=39038>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=39038 Summary: During Tomcat 5.5.16 startup/shutdown, order of executing between session and context listeners is backwards. Product: Tomcat 5 Version: 5.5.16 Platform: All OS/Version: Windows XP Status: NEW Severity: normal Priority: P2 Component: Unknown AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] CC: [EMAIL PROTECTED] On Tomcat 5.5.16 startup, listener classes that implement the HttpSessionAttributeListener interface are being called before classes that implement the ServletContextListener interface. On shutdown, classes that implement HttpSessionAttributeListener (e.g. sessionWillPassivate method) are called before classes that implement the ServletContextListener interface. After reading section SRV.10.3.3 (Listener Registration) and SRV.10.3.4 (Notifications At Shutdown) of the 2.4 servlet spec, I believe the order of these invocations are backwards. Shutdown in the spec is very clear, in that it states "Session listeners must be notified of session invalidations prior to context listeners being notified of application shutdown." While not as clear, I believe that it only makes sense during startup that context listeners should be notified before session attribute listeners. The behavior that I believe it correct is what is being done in Tomcat 5.5.9. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
