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=5585>. 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=5585 Error page not displayed [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2002-01-07 12:03 ------- This is a user error, for the reasons explained below -- therefore I am marking this bug report as INVALID. See below for user workarounds to get more useful diagnostics. This is what is happening to cause the behavior that you see: * Your calling page includes the action: <jsp:include page="test_2.jsp"/> * Because you did not include a "flush" attribute, it defaults to "true" -- just as if you had said: <jsp:include page="test_2.jsp" flush="true"/> * The effect of flushing is to cause the response to be committed. After the response is committed, it is no longer possible for the container's error page mechanism to display an error page. Workarounds to ensure that you see compile errors: * Call the "test_2.jsp" page directly from your browser, to make sure that it compiles correctly. * Turn flushing off: <jsp:include page="test_2.jsp" flush="false"/> * Put the <jsp:include> inside a try/catch block and catch the ServletException that is thrown when Jasper discovers the compile error. * Look in the Tomcat log files, because they will contain the compile exception stack trace even if the response has already been committed. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
