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 2001/09/26 03:57:26 UTC

DO NOT REPLY [Bug 3776] - "Illegal to flush within a custom tag" exceptions

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

"Illegal to flush within a custom tag" exceptions

craig.mcclanahan@sun.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX



------- Additional Comments From craig.mcclanahan@sun.com  2001-09-25 18:57 -------
Without seeing your stack trace, it is impossible to know what the problem is
for certain.  However, there was a significant change between 4.0-b7 and 4.0
final that *might* have been related.

The JavaDocs for the PageContext.include() method include the statement:

    "The current JspWriter "out" for this JSP is flushed
    as a side effect of this call, prior to processing
    the include."

Tomcat 4.0-b7 did not correctly implement this method, because it didn't do the
flush.  Flushing the response was added in Release Candidate 1 in order to be
compliant with the specification requirments.

If you don't believe that this was the cause of your problem, please reopen this
bug report - but in order to be able to debug it, you should provide an example
JSP page that illustrates the problem, plus the stack trace that is generated. 
Without this, little useful debugging is possible.