Part of the spec says if no error-page declaration containing an
exception-type fits using the class-heirarchy match, and the exception
thrown is a ServletException or subclass thereof, the container extracts the
wrapped exception...
So supposing for a minute that Tomcat internals ignore any
From: Mike Curwen [EMAIL PROTECTED]
I've successfully caught 'all other' exceptions (which I suppose must
include ServletExceptions), by using one error-page declaration that
catches
status-code500/status-code, and then multiple exception-type's to
catch more specific exception types.
Thanks,
