Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: domain of wheleph@gmail.com designates
 209.85.216.180 as permitted sender)
MIME-Version: 1.0
From: Volodymyr Sobotovich <wheleph@gmail.com>
Date: Tue, 9 Aug 2011 22:55:19 +0300
Message-ID: 
 <CAFaTLCBgacZEvPAsqd=2-xF7n9bwcUORbMaHgMbe-z1GZ=WWVg@mail.gmail.com>
Subject: ServletRequestListener.requestDestroyed is called before request
 leaves a webapp
To: dev@tomcat.apache.org
Content-Type: text/plain; charset=UTF-8

Hello, everyone.

I think I have found a bug in Tomcat's lifecycle handling of
ServletRequestListener. I'd like to discuss it here before posting.
Tomcat 7.0.19, jdk 1.7.0-b147, Ubuntu Linux 11.04
Steps to reproduce:
1. declare error page for 404 code in web.xml
2. Set location of that page to some servlet (let's call it ErrorServlet)
3. go to any invalid URL in webapp (to cause 404)
4. ErrorServlet is called after requestDestroyed on any registered listener.
This kind of behaviour is not correct in my opinion because it
contradicts to contract of ServletRequestListener.
Also it breaks org.springframework.web.context.request.RequestContextListener
if ErrorServlet uses session-scoped beans.

What do you think about that. Should I post in to Bugzilla?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org