tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 16319] New: - RequestDispatcher.include in a customTag causes IllegalStateException
Date Wed, 22 Jan 2003 11:18:50 GMT
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=16319>.
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=16319

RequestDispatcher.include in a customTag causes IllegalStateException

           Summary: RequestDispatcher.include in a customTag causes
                    IllegalStateException
           Product: Tomcat 4
           Version: 4.1.8
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Critical
          Priority: Other
         Component: Servlet & JSP API
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: tomasz@rtsoftware.com


In my own Tag that uses RequestDispatcher.include to make the actual include I 
get:

java.lang.IllegalStateException: getOutputStream() has already been called for 
this response

in the JSP after the content written into the original output stream reaches 
the size that requires flushBuffer() method of 
org.apache.jasper.runtime.JspWriterImpl.

jsp:include works, but this is not a solution, since we want to have a cross-
context includes. 

I have seen that Jasper wrapps the response into ServletResponseWrapperInclude 
to make jsp:include, I guess this is what is missing with 
RequestDispatcher.include.

I cannot use the same approach, since the same JSP needs to work with WebLogic, 
too.

--
To unsubscribe, e-mail:   <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@jakarta.apache.org>


Mime
View raw message