----- Sender's Comment ----- g trouvé ça dans les bug report de tomcat... pourtant je crois avoir une version qui est sensée marcher... ----- End Of Sender's Comment --------------------------- Report URL: <http://znutar.cortexity.com/BugRatViewer/ShowReport/95> Report #95 Details Project: Tomcat Category: Bug Report SubCategory: New Bug Report Class: swbug State: closed Priority: high Severity: serious Confidence: public Environment: Release: tomcat 3.2 beta/3.3 dev JVM Release: any Operating System: any OS Release: any Platform: any Synopsis: error-page handling doesn't work Description: I've specified an error-page element in web.xml for exception-type javax.servlet.ServletException. But, when a request is made to a servlet that throws a ServletException, the servlet mapped to the location I specified is never invoked. Instead, tomcat's default error handler is invoked. This used to work in Tomcat 3.1. I found the cause of this behaviour in a simple typo in ContextManager.java. I've included a patch in the Known Work Around section of this bug report. In Tomcat 3.1, I also used to be able to specify a jsp file as the location in an error-page element. This does not work in tomcat 3.2 beta even after this simple patch is applied. The JspServlet is selected correctly, but the request's servlet path matches that of the error-originating request, not that of the error-page so the JspServlet reports that it cannot find the jsp file. I'm not sure which is the appropriate fix for this secondary problem, either to invoke the error servlet with a request dispatcher or to use internal mechanisms to reproduce what the request dispatcher does. Something along those lines should take care of it though.Title: BugRat Report # 95
BugRat Report # 95
| Project: Tomcat | Release: tomcat 3.2 beta/3.3 dev |
| Category: Bug Report | SubCategory: New Bug Report |
| Class: swbug | State: closed |
| Priority: high | Severity: serious |
|
Confidence:
public
|
Submitter:
Joel Bartley ( [EMAIL PROTECTED] )
Date Submitted:
Sep 10 2000, 01:02:53 CDT
Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )
- Synopsis:
- error-page handling doesn't work
- Environment: (jvm, os, osrel, platform)
- any, any, any, any
- Additional Environment Description:
- Report Description:
- I've specified an error-page element in web.xml for exception-type javax.servlet.ServletException. But, when a request is made to a servlet that throws a ServletException, the servlet mapped to the location I specified is never invoked. Instead, tomcat's default error handler is invoked. This used to work in Tomcat 3.1. I found the cause of this behaviour in a simple typo in ContextManager.java. I've included a patch in the Known Work Around section of this bug report. In Tomcat 3.1, I also used to be able to specify a jsp file as the location in an error-page element. This does not work in tomcat 3.2 beta even after this simple patch is applied. The JspServlet is selected correctly, but the request's servlet path matches that of the error-originating request, not that of the error-page so the JspServlet reports that it cannot find the jsp file. I'm not sure which is the appropriate fix for this secondary problem, either to invoke the error servlet with a request dispatcher or to use internal mechanisms to reproduce what the request dispatcher does. Something along those lines should take care of it though.
- Workaround:
