Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 6501 invoked from network); 24 Apr 2003 19:47:24 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 24 Apr 2003 19:47:24 -0000 Received: (qmail 26766 invoked by uid 97); 24 Apr 2003 19:49:25 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@nagoya.betaversion.org Received: (qmail 26759 invoked from network); 24 Apr 2003 19:49:25 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by nagoya.betaversion.org with SMTP; 24 Apr 2003 19:49:25 -0000 Received: (qmail 5080 invoked by uid 500); 24 Apr 2003 19:47:09 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 5068 invoked from network); 24 Apr 2003 19:47:09 -0000 Received: from rwcrmhc51.attbi.com (204.127.198.38) by daedalus.apache.org with SMTP; 24 Apr 2003 19:47:09 -0000 Received: from micron.ix.netcom.com (12-236-186-207.client.attbi.com[12.236.186.207]) by rwcrmhc51.attbi.com (rwcrmhc51) with SMTP id <20030424194713051001a81fe>; Thu, 24 Apr 2003 19:47:14 +0000 Message-Id: <4.3.1.0.20030424121613.00d5c9a0@popd.ix.netcom.com> X-Sender: djonesca@popd.ix.netcom.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Thu, 24 Apr 2003 13:13:54 -0700 To: "Tomcat Users List" From: Dave Jones Subject: problem with page display after migrating to Tomcat 4.1.24 Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=====================_17214464==_.ALT" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N --=====================_17214464==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed Hi, I'd like to try this request for help again (still stuck after trying 4.1.24). I've run into a problem migrating an application from Tomcat 3.3 to 4.1.24. Briefly, the problem is that my JSP pages, which include several jsp:include tags, stop displaying at the first include when an exception is thrown by a later include. Example:

<----- (A)

body.jsp contains html, jsp scriptlets and tags and calls to beans. If body.jsp does not throw an exception, the page displays fine. However, if body.jsp throws an exception, the page only displays up to point A above. If I remove the include tag for header.jsp, a stack trace is displayed (as expected). If I replace the include tag with code from the included header.jsp, a stack trace is displayed (as expected). The problem only occurs when a) an exception is thrown from body.jsp and b) the header code is included via jsp:include instead of placed in-line. Can anyone shed some light on this? TIA, Dave Jones NetEffect --=====================_17214464==_.ALT--