DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=34513>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=34513 Summary: jsp exception handling Product: Tomcat 5 Version: 5.0.28 Platform: All OS/Version: Windows XP Status: NEW Severity: normal Priority: P2 Component: Jasper AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] I use the following directive <%@ page errorPage="/jsp/error.jsp" %> to tell jsp to move to error.jsp when exception raises on the page. But I noticed the the real behavior relates to the "position" that the exception raises on the JSP page: 1.When it raises on the relatively front part of the page, the page is redirected correctly to /jsp/error.jsp 2.if exception raises at relatively rear position, the contenct of the /jsp/error.jsp is outputed right after the normal output of the page. 3.If at even rearer position, the result is a weird "chopped" page with only part of normal output. I tried to debugged the src of jasper into PageContextImpl's doHandlePageException method. Found that the situation 2 was caused by "JspWriterImpl has already flushed", the situation 3 was caused by the "response was already committed". I can't understand this behavior of tomcat. Isn't it puzzling to the ones that want to debug JSP page? -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
