tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Larry Isaacs <Larry.Isa...@sas.com>
Subject RE: Hello? Anybody?
Date Thu, 02 Nov 2000 19:34:47 GMT
Thanks Craig,

To support this behavior, should the spec require that for a JSP that is
"included" or "forwarded", handlePageException() is required to propagate
the exception back to the caller?  Currently, it just says that if there is
no error page, it should "perform some implementation dependent action."
Was the "implementation dependent action" intended only for the original,
i.e. non-"included" and non-"forwarded", servlet or JSP?

Larry

-----Original Message-----
From: Craig R. McClanahan [mailto:Craig.McClanahan@eng.sun.com]
Sent: Thursday, November 02, 2000 1:28 PM
To: tomcat-dev@jakarta.apache.org
Subject: Re: Hello? Anybody?


Ethan Wallwork wrote:

> Since the spec implies that exceptions should be thrown from a
> RequestDispatcher call rather than handled, and there seems to be nothing in
> the spec that forbids this behavior, I would like to see it implemented this
> way.  Does anyone know of any reasons it shouldn't be done this way?
>

My understanding of the spec is that a ServletException or IOException that is
thrown by a servlet included (or forwarded to) by a RequestDispatcher should be
propogated up to the calling servlet.  Any other exception (like
IllegalStateException, NullPointerException, etc.) that the included/forwarded
servlet throws should be wrapped in a ServletException, and that exception should
be thrown.  This is the way 4.0 works.

If 3.2 doesn't do this, IMHO that is a bug.

>
> --
> Ethan
>

Craig McClanahan

[snip]

Mime
View raw message