Len Popp wrote:
You can use an directive in web.xml to send uncaucht
exceptions to an error page:
java.lang.Exception
/error
Thanks Len, but I want to do more than catch them, I want to also report
on them -- is the exception accessible on the resulting page?
On 2/3/06, Mott Leroy <[EMAIL PROTECTED]> wrote:
> Glen Mazza wrote:
>
> >> And another is to define the error page in your web.xml:
> >>
> >>
> >> 500
> >> /myPage.jsp
> >>
> >>
> >
> > I would save these for generic HTTP error codes, or generic Java
> > exceptions (NullPointerErrors,
Glen Mazza wrote:
And another is to define the error page in your web.xml:
500
/myPage.jsp
I would save these for generic HTTP error codes, or generic Java
exceptions (NullPointerErrors, ClassCastExceptions, perhaps), things are
more likely the result of errors in coding than
Mott Leroy wrote:
I am on Tomcat 5.0.x
I am familiar with a couple ways to capture errors that occur on the JSP
side. One way is to use the error page tag:
<%@ page errorPage="MyErrorPage.jsp" %>
Chapter 10 on exception handling, Beginning JavaServer Pages (Wrox
Books, 2005), I think wou
I am on Tomcat 5.0.x
I am familiar with a couple ways to capture errors that occur on the JSP
side. One way is to use the error page tag:
<%@ page errorPage="MyErrorPage.jsp" %>
And another is to define the error page in your web.xml:
500
/myPage.jsp
I've inherited a vast
