Java Mailing List Archive

http://www.junlu.com/

Home » Home (12/2007) » Apache Tomcat »

Re: Jasper Gobbling exceptions

Rob Adamson

2007-07-25

Replies:

On 11/07/07, Berglas, Anthony <aberglas@(protected):
> When I call a JSP directly via web.xml exceptions provide a number of
> "root cause" stack traces the second or third of which indicates what
> the exception actually was and, with some deciphering, which .tag file
> generated it. The trace is shown on both the form and Tomcat standard
> output, which is handy.
>
> However when I call the JSP from a Servlet only the first, useless,
> JasperException is displayed. On has to go to the Tomcat log to see the
> real exception. This happens regardless of whether .forward or .include
> is used.
>
> Is it possible to invoke the JSP via the servelet and still get the
> underlying exception? (Would be handy during development.)

Could you set an error page on the JSP? This could then output the
full exception chain.

Rob

---------------------------------------------------------------------
To start a new topic, e-mail: users@(protected)
To unsubscribe, e-mail: users-unsubscribe@(protected)
For additional commands, e-mail: users-help@(protected)

©2008 junlu.com - Jax Systems, LLC, U.S.A.