File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes JSP and the fly likes Problems with Exception Handling via web.xml config Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Java Interview Guide this week in the Jobs Discussion forum!
JavaRanch » Java Forums » Java » JSP
Bookmark "Problems with Exception Handling via web.xml config" Watch "Problems with Exception Handling via web.xml config" New topic

Problems with Exception Handling via web.xml config

Mark Vedder
Ranch Hand

Joined: Dec 17, 2003
Posts: 624

Hello All,
I'm tying to configure a Web App to use specific Error pages for particular exceptions, but I am running into problems.
On Sun ONE Web Server v6.1 (Servlet 2.3 / JSP 1.2) I have the following web.xml: Extends java.sql.SQLException
A bean used by various JSP pages in the app can throw
From my understanding, the container should use the most appropriate <error-page> entry to handle an exception. So when my Bean throws the, the container should forward it to MySpecialException.jsp. Well it doesn't; it goes to the GeneralExceptions.jsp page (the planned catch all page). A on that page displays Message Details - so I know the container is �seeing� the proper exception type.
Now if I comment out the Throwable entry in the web.xml:

I get the MySpecialException.jsp - but this eliminates the ability to handle the unforeseen exceptions that the GeneralExceptions.jsp page was meant to handle.
What am I missing here? Why is the container not using the specified page?
A big thank you in advance for any and all Assistance
Frank Carver

Joined: Jan 07, 1999
Posts: 6920
My guess is that the JSP code is probably wrapping the actual thrown exception into a ServletException of some sort before it reaches your error pages. Try printing exception.getClass() in the catch-all JSP and seeing which class the exception really is.

Read about me at ~ Raspberry Alpha Omega ~ Frank's Punchbarrel Blog
Mark Vedder
Ranch Hand

Joined: Dec 17, 2003
Posts: 624

Thanks for the suggestion.
A <%= exception.getClass() %> is displaying class
However, the container's error log does show:
[17/Dec/2003:13:59:11] failure ( 360): for host trying to GET /dbgui/process.jsp, service-j2ee reports: StandardWrapperValve[jsp]: WEB2792: Servlet.service() for servlet jsp threw exception
javax.servlet.ServletException: My Bean's Specialized Message
----- Root Cause ----- My Bean's Specialized Message

Sorry that I missed that before. Any suggestions on how to work around this? I suppose I could catch the ServletException and then search the message string for key words to determine if I need to forward to the Special Error Page (or what error page to go to), but it seems like there should be an easier way (especially since I have different messages and they may change in the future - especially when the page is localized). Any suggestions.
I agree. Here's the link:
subject: Problems with Exception Handling via web.xml config
It's not a secret anymore!