Before I add an errorPage parameter to each one of my JSPs, I'd like to be
sure that I'll still be able to see the stack trace of any exceptions that
may happen. By default (without setting an errorPage) Orion seems to show
them, but the jswdk just gives you "Error 500".
I started at http://java.sun.com/products/jsp/html/exceptions.fm.html -- on
this page it says that "exception.printStackTrace() displays the exception's
stack trace. The class name and stack trace are probably very helpful to you
the developer, but probably not very helpful to your user." I'd take this
to mean that the stack trace is sent to the browser, but when I run the
example I only see it in the error stream of the java web server.
printStackTrace() can take a java.io.PrintStream, but
javax.servlet.jsp.JspWriter is extended from Writer, not OutputStream so I
don't think casting is a solution.
I'd agree with the tutorial that the stack trace is not something that the
end user is going to want to see, but while I'm developing I'd rather not
have to do anything extra to see the trace if I'm not running the web server
locally.
Thanks for any ideas,
Jeff
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
