Hi
I've sent this earlier to servletapi-feedback. Thanks
for any suggestion you might have.
> according to the 2.2 spec, section 8.5
>
> > Only runtime exceptions and checked exceptions of
> > type ServletException or
> > IOException should be propagated to the calling
> > servlet if thrown by the target of a request
> > dispatcher.
>
> Does that mean that this try block should catch the
> runtime exception deliberately raised by the "error"
> servlet?
>
> try{
> getServletConfig().getServletContext().
> getRequestDispatcher("/servlet/error").
> include(request, response);
> } catch (Exception ex) { ex.printStackTrace (); }
>
> This doesn't seem to happen in Tomcat 3.1 (instead,
> I
> see error 500 in included servlet). Should I expect
> the catch to happen in the standard?
>
> thank you,
>
> Cristian
>
> ps. this mail should have gone to Tomcat developers
> as
> well, but Jakarta seems to be down and I can't find
> their address
__________________________________________________
Do You Yahoo!?
Send instant messages & get email alerts with Yahoo! Messenger.
http://im.yahoo.com/
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
