Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org Received: (qmail 3647 invoked by uid 500); 25 Jun 2001 13:35:01 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk Reply-To: tomcat-user@jakarta.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 3609 invoked from network); 25 Jun 2001 13:34:58 -0000 Received: from haydn.spinweb.net (161.58.226.153) by h31.sny.collab.net with SMTP; 25 Jun 2001 13:34:58 -0000 Received: from rsand ([213.203.43.194]) by haydn.spinweb.net (8.11.2) id f5PDYwd35779; Mon, 25 Jun 2001 07:34:58 -0600 (MDT) Message-ID: <01ec01c0fd7b$7b73df50$0101010a@netegrity.com> From: "Richard Sand" To: Subject: bizarre page flushing situation Date: Mon, 25 Jun 2001 15:33:49 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Hi all- I've got the following somewhat whacky setup which Tomcat refuses to handle. It involves custom tags and included JSP pages. My tomcat is 3.2.2 on W2K running native (i.e. no external web server). At the bottom of all of my JSP pages I include a JSP footer as follows: <%@ include file="/footer.jsp" %> Inside footer.jsp, I display a footer that is customized to whether the user is logged in, which is determined by custom tags. Footer.jsp looks as follows: So here's the problem: I get the exception: java.io.IOException: Illegal to flush within a custom tag but ONLY when I use those particular custom tags inside the footer. If I use them in the main jsp pages they work fine. I also tried removing the flush=true, but tomcat replies: org.apache.jasper.compiler.CompileException: ... jsp:include needs to have "flush=true" On other application servers, I didn't have the flush=true and they worked fine. Lastly, the doAfterBody of the tags is very basic: try { // write the body and return SKIP_BODY bodyContent.writeOut(bodyContent.getEnclosingWriter()); return SKIP_BODY; } catch (Exception e) { throw new JspException(e.toString()); } Can anyone explain this behavior??? Thanks for your help! Best regards, Richard