You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2006/03/02 14:03:49 UTC
DO NOT REPLY [Bug 38829] New: - spec violation?
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=38829>.
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=38829
Summary: spec violation?
Product: Tomcat 5
Version: 5.5.12
Platform: Other
OS/Version: Windows 2000
Status: NEW
Severity: critical
Priority: P1
Component: Servlet & JSP API
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: dnavitaniuk@fastmail.fm
I think I found issue with error-page processing...
if the "exception-thrower" jsp contains <%@ page ...errorPage="error.jsp"%>
and it generates lots of output, I receive the
SEVERE: Exception Processing ErrorPage[exceptionType=java.lang.Throwable,
location=/error.jsp]
java.lang.IllegalStateException
at org.apache.coyote.Response.reset(Response.java:296)
at org.apache.catalina.connector.Response.reset(Response.java:642)
at org.apache.catalina.connector.Response.reset(Response.java:908)
it isnt quite good for me but at least it is understandable
what I think isnt is the following:
if there was a small output prior to exception occurence with conditions above
then error.jsp is working with wrapped request/response...
if I remove a explicit error.jsp form "page" attributes in jsp then error.jsp is
working with unwrapped request/response...
please take a look at 38826 sor clarifications
--
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: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
DO NOT REPLY [Bug 38829] - spec violation?
Posted by bu...@apache.org.
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=38829>.
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=38829
william.barker@wilshire.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
------- Additional Comments From william.barker@wilshire.com 2006-03-03 05:39 -------
<spec-quote spec="JSP" version="2.0" section="1.4.2">
Any uncaught exceptions thrown in the body of the JSP page implementation
class result in the forwarding 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).
</spec-quote>
The JSP spec and the Servlet spec don't match up on this point (complain to
one, the other, or both: but we just implement it here :). The use
of 'forwarding' in this context means that for JSP errors you get the wrapped
request/response when an errorPage is specified. However, the 'implementation
default' is to pass the unwrapped request/response.
Hopefully somebody will care enough to pass this on to:
jsp-spec-comments@eng.sun.com
so we can get some clarity here :).
--
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: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org