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] - exception object is null inside an error page
Date Wed, 19 Jun 2002 11:42:50 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

remm@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WORKSFORME



------- Additional Comments From remm@apache.org  2002-06-19 11:42 -------
I don't understand why it doesn't work. The error page is only invoked when 
there is an exception (assuming you didn't set it for status codes also), which 
is retrieved using a getAttribute method call (attribute name 
is "javax.servlet.error.exception"). Then the attribute is correctly passed in 
the request dispatcher to your error page.

There are also test cases for that functionality (very similar use cases) in 
the tester and Watchdog.

If it still doesn't work for you, please provide a complete test case.

--
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