tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 9980] New: - exception object is null inside an error page
Date Wed, 19 Jun 2002 06:06:46 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9980>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9980

exception object is null inside an error page

           Summary: exception object is null inside an error page
           Product: Tomcat 4
           Version: 4.0.4 Final
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Servlet & JSP API
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: steve5m@yahoo.com


I have a custom error page, which at the top has
<%@ page isErrorPage="true" %>

Given this declaration, when my error page is called
(because I configured it as the error page for all errors
in web.xml)
it should be able to use the built-in variable called 'exception'
according to the Servlet 2.2/2.3 spec.
However, in all of my testing so far, this 'exception' varaiable
turns out to be null -- same code run on Tomcat 3.3.1 never has this
problem, and I see no reason for this object to be null (unless the
page was called where there really is no exception, but I make sure
one was thrown).  Anyway, this bug pretty much prevents me from having
my custom error page.

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


Mime
View raw message