DO NOT REPLY [Bug 16181] New: - JspWriter not restored properly when exception thrown in a tag's body content

[bu...@apache.org]

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=16181>.
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=16181

JspWriter not restored properly when exception thrown in a tag's body content

           Summary: JspWriter not restored properly when exception thrown in
                    a tag's body content
           Product: Tomcat 4
           Version: 4.1.18
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Jasper 2
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: pierre.delisle@sun.com


If an exception is thrown in the body content of a tag,
and this tag is wrapped around a <c:catch>, the 
JspWriter is not properly restored with Jasper2
(with our without pooling enabled).

The example below fails to output properly anything sent to the
JspWriter after the exception is thrown. 
Tested with tomcat 4.1.18 and JSTL 1.0.3 (currently the nightly
of 'standard' at jakarta-taglibs).

-----
<%@ taglib prefix="c" uri="http://java.sun.com/jstl/core" %>

<%!
   public String throwEx() throws Exception {
      throw new java.lang.Exception("exception thrown by throwEx");  
   }
%>

<h3>begin</h3>

<c:catch var="ex2">
  <c:out value="${null}">
    <% throwEx(); %>
  </c:out>
</c:catch>
<c:out value="${ex2}" default="exception is null - 2" escapeXml="false"/>

<h3>end</h3>

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>