Hi Jan - Apparently this problem is fixed in Tomcat 5. Tomcat 4.1.30
has the following code which has the effect I outlined below (losing the
stack trace of the original exception). Yet another example of why it is
necessary to test a webapp on all versions of the platform it may be
deployed on.
When I throw a JspException from a custom tag the PageContext
handlePageException() method wraps it in a ServletException and then
Tomcat JspServletWrapper.service() wraps that in a JasperException
(which is also a ServletException). So the original exception is 3 deep
and the stack trace of the
