tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 4542] - jsp:include inside a custom tag can throw an exception.
Date Thu, 06 Dec 2001 18:53:56 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4542>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4542

jsp:include inside a custom tag can throw an exception.





------- Additional Comments From kin-man.chung@sun.com  2001-12-06 10:53 -------
Let me use a specific example to make sure I understand what you are talking
about.  A.jsp includes B.jsp, and the errorPage for A.jsp is A.err.jsp, and that
for B.jsp is B.err.jsp.  An exception is thrown in B.jsp, and you expect the
exception to be handled by A.err.jsp (not B.err.jsp).

I do not agree.  It is certainly not the way Java exceptions work, where
exceptions handlers are searched in the called method first, and then in calling
methods; but once a handler is found in the called method, the exception is
considered handled, and the handlers in the calling mehtod are not considered. 
The current Jasper is structured in such a way, and I suspect it would be hard
to do it the other way.

I have seen the "Document contains no data" in other context before, but thought
was fixed.  Go ahead and file a bug if it happens again.

--
To unsubscribe, e-mail:   <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@jakarta.apache.org>


Mime
View raw message