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=42934>. 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=42934 ------- Additional Comments From [EMAIL PROTECTED] 2007-08-01 08:27 ------- You missed my point. The order in which the listeners are called depends (in part) on the order in which they are declared. The behaviour that you describe could be perfectly correct according to the servlet spec, *depending on how the listeners are declared*. For more details, see section 10.3.3 and 10.3.4 of the servlet specification. Here is a concrete example. Suppose web.xml contains these declarations: <listener> <listener-class>com.example.MySessionListener</listener-class> </listener> <listener> <listener-class>com.example.MyContextListener</listener-class> </listener> In this example, on startup the session listener will be called before the context listener (according to section 10.3.3 of the servlet spec). On shutdown, the session listener will again be called before the context listener (according to section 10.3.4). Another possibility is that a single listener class implements two listener interfaces. In that case, the spec doesn't say what order they should be called on startup. I guess if the listeners need to be called in a certain order, they need to be implemented in separate classes so that you can specify the order. So, how are the listeners declared in your case? Please post the contents of web.xml, or just the part with the <listener> declarations. -- 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]
