Hi, I think this is according to the spec. It took us a while to sort this out, and several consultations with the JSP Spec leads. It's related to those new filter mapping types defined in Spec version 2.4.
Yoav Shapira http://www.yoavshapira.com >-----Original Message----- >From: Rick Wong [mailto:[EMAIL PROTECTED] >Sent: Wednesday, October 13, 2004 8:14 PM >To: Tomcat Users List >Subject: Problem with web.xml <error-page> not invoking servlet filter > >Hi, > >I am using Tomcat 5. In my application, my web.xml declares a <filter>, >and a global error page > ><error-page> > <exception-type>java.lang.Exception</exception-type> > <location>/error.jsp</location> ></error-page> > >By examining the call stack in my error page JSP, I notice that when >this error page is invoked, my filter is not called. However, if I >define <%@ page errorPage="/error.jsp" %> in my JSP file, my <filter> is >invoked (and as a part of the call stack). > >Is this a Tomcat bug? Or does this behavior conform with the Servlet >2.4 spec? > >Thanks, >-- >Rick > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
