https://issues.apache.org/bugzilla/show_bug.cgi?id=57314
--- Comment #5 from Jozef Hartinger <jozefhartin...@gmail.com> --- I am really disappointed by this resolution. First of all: "Interface for receiving notification events about requests coming into and going out of scope of a web application." When a request goes async and the processing is moved somewhere else, it clearly is the case that the processing has gone out scope of a web application (the servlet container knows nothing about where the processing continues). Therefore, the destroyed callback should be called at this point. The request stays out of the scope of the web application until it is dispatched to the web application again. Secondly, ServletRequestListener seems to be the portable hook for integrating various frameworks that use ThreadLocals and it actually is portable across Servlet implementations except for Tomcat. Lastly, nice to know that there is a proprietary hook for doing this. It however still makes integration much more painful compared to the portable one. Would it be possible to consider adding a mode or a configuration option that, when set, would change Tomcat's behavior to align with all the other Servlet implementations? -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
