DO NOT REPLY [Bug 4542] - jsp:include inside a custom tag can throw an exception.
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. [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2001-12-11 04:13 --- Thanks for the clarification. I have put the bug into FIXED state which I hope is the right thing to do. As far as I am concerned the bug that I raised has been fixed. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 4542] - jsp:include inside a custom tag can throw an exception.
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 [EMAIL PROTECTED] 2001-12-10 18:32 --- The servlet error page specified in the deployment descriptor is a global error handler, whereas the error page specified in a jsp page directive is error handler local to the page. Therefore the servlet spec does not apply to a JSP page, which has it own rules governing errors. Section JSP 2.4.2 states, Any uncaught exceptions thrown in the body of the JSP page implementation class result in the fowarding of the client request and uncaught exception to the errorPage URL specified by the JSP page (or the implementation default behavior, if none is specified). It clearly indicates that errors occur in a page should be handled by its errorPage, if specified. In fact, the error page specified in the servlet deployment descriptor need not be used, even if an errorPage is not specified in a JSP page, since the implementation default behavior may choose to just report the error without setting the error code in the response. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 4542] - jsp:include inside a custom tag can throw an exception.
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 [EMAIL PROTECTED] 2001-12-07 06:59 --- What about the inconsistency between servlets and JSP which are really just Servlets themselves ? As I mentioned above the Servlet specification clearly states that error pages are not used if the servlet in which the exception occurs has been called from another servlet using the RequestDispatcher, instead it goes back to the top level servlet which handled the original request. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 4542] - jsp:include inside a custom tag can throw an exception.
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. [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED | --- Additional Comments From [EMAIL PROTECTED] 2001-12-06 03:21 --- I have tested this and the test case I supplied does work as I expected it too. Unfortunately I think that my expectations were wrong. If an error occurs in the included page my test case expected the error page in the included page to be used but I think that the test page in the included page should be ignored and the exception should be passed up to the top level page which should handle it. The Servlet 2.3 specification states in SRV.9.9.2 error pages The error page mechanism described does not intervene when errors occur in servlets invoked using the RequestDispatcher. In this way, a servlet using the RequestDispatcher to call another servlet has the opportunity to handle errors generated in the servlet it calls. The JSP specification does not cover this situation though so it is probably open to interpretation although the reasoning behind the statement in the servlet specification. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 4542] - jsp:include inside a custom tag can throw an exception.
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 [EMAIL PROTECTED] 2001-12-06 03:40 --- continued from above... seems quite reasonable. The including page knows that it is including another page and so can make sure that the error page can cope with an error from the included page but the included page does not know whether or not it is included inside another page or not so its error page might not provide enough information. I am not sure if this is related or is a new bug but the default error page processing does not seem to be working. A JSP page which throws an exception but does not have an error page specified results in a Document contained no data. message from Netscape. If this is a new bug and not related to this one then could you let me know whether there is a bug open on this already and if so what its number is and if not I will open a new one. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 4542] - jsp:include inside a custom tag can throw an exception.
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 [EMAIL PROTECTED] 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:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 4542] - jsp:include inside a custom tag can throw an exception.
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. [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2001-12-05 10:26 --- Fixed in 20011205 nightly build. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 4542] - jsp:include inside a custom tag can throw an exception.
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. [EMAIL PROTECTED] changed: What|Removed |Added CC||tomcat- ||[EMAIL PROTECTED] AssignedTo|tomcat- |[EMAIL PROTECTED] |[EMAIL PROTECTED] | --- Additional Comments From [EMAIL PROTECTED] 2001-11-02 13:54 --- I am not sure I understand what the problem is. Are you saying that if you have a jsp:include inside the body of a custom tag, and you do a out.write () after that, you get an exception? Please give a test case, something concrete that I can verify. Thanks. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
