Tomcat 4 will never match:
<error-page>
<exception-type> java.io.IOException </exception-type>
<location> /ioexception.html </location>
</error-page>
because all servlet-generated IOExceptions are silently
swallowed up by StandardWrapperValve before they get a
chance to be handled by the ErrorReportValve. (or the
ErrorReportValve, you don't even get the default stack
trace page)
This strikes me as bad, but there are comments in the
StandardWrapperValve code that indicate it's intentional.
I've searched fruitlessly (google, list archives, cvs
comments, etc) for any hints about why Tomcat would
want to do this.
Is is a bug or a feature? If it's a bug, I'll happily
submit a bugreport and patch. If it's a feature, what's
the rationale?
Thanks,
--
Christopher St. John [EMAIL PROTECTED]
DistribuTopia http://www.distributopia.com
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
