It could be that the error page itself is throwing an error. Try using an ultra-simple error page. -- Len
On 5/18/06, Zohar <[EMAIL PROTECTED]> wrote:
No, I've used the "Letting a page define its error page" option. ----- Original Message ----- From: "Franck Borel" <[EMAIL PROTECTED]> To: "Tomcat Users List" <users@tomcat.apache.org> Sent: Thursday, May 18, 2006 14:20 Subject: Re: error page > > >> I'm trying to use the error handling mechanism described in >> http://java.sun.com/developer/EJTechTips/2003/tt0114.html. >> When an exception in thrown in JSP1 it is indeed redirected to JSP2. in >> JSP2 I've put "System.out.println(exception.getMessage());" and sure >> enough the exception's message is printed. But what I get as a response >> to the browser is "HTTP 500". >> > > Have you make an entry like this in your Web deployment descriptor > (web.xml)? > > <!-- Catch a system error using an HTML page --> > <error-page> > <exception-type>your.exception. > </exception-type> > <location>/JSP2.jsp</location> > </error-page> > > > -- Franck > > > -------------------------------------------------------------------------------- > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
