Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@www.apache.org Received: (qmail 71665 invoked from network); 1 Mar 2005 12:16:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 1 Mar 2005 12:16:40 -0000 Received: (qmail 59665 invoked by uid 500); 1 Mar 2005 12:16:23 -0000 Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org Received: (qmail 59636 invoked by uid 500); 1 Mar 2005 12:16:22 -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 59619 invoked by uid 99); 1 Mar 2005 12:16:22 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from coffee.shu.ac.uk (HELO coffee.shu.ac.uk) (143.52.2.44) by apache.org (qpsmtpd/0.28) with ESMTP; Tue, 01 Mar 2005 04:16:22 -0800 Received: from crocus.shu.ac.uk ([10.14.72.51] helo=exchange.shu.ac.uk) by coffee.shu.ac.uk with esmtp (Exim 4.42) id 1D66F2-0001UL-LI for tomcat-user@jakarta.apache.org; Tue, 01 Mar 2005 12:12:44 +0000 Received: from snowdrop.shu.ac.uk ([143.52.2.23]) by exchange.shu.ac.uk with Microsoft SMTPSVC(5.0.2195.6713); Tue, 1 Mar 2005 12:11:33 +0000 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Tue, 1 Mar 2005 12:11:33 -0000 Message-ID: <5DA47C36E7C8004A994D19FC6E77DBE117F561@snowdrop.shu.ac.uk> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Change in JSP error handling in Tomcat5.0?? Thread-Index: AcUeV887h2RpCua4StKd0+BFvfQh7w== From: "Graba, Jan" To: X-OriginalArrivalTime: 01 Mar 2005 12:11:33.0778 (UTC) FILETIME=[CF3CBF20:01C51E57] X-SHU-MailScanner-Information: Please contact the ISP for more information X-SHU-MailScanner: Found to be clean X-Spam-Status: X-MailScanner-From: cmsjg3@exchange.shu.ac.uk Subject: Change in JSP error handling in Tomcat5.0?? X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hi. While testing a JSP error page that was working fine 9 months ago, I = found that the page is not now performing its function. Instead of displaying an appropriate error message when the associated = JSP receives alphabetic data instead of the integer data that it is expecting, an HTTP 500 message saying that the data = manipulation JSP cannot be displayed is generated by the browser.=20 The simple application behaves fine when valid data is entered, and the = JSP error page itself can be rendered directly (if a suitable check is made for the implicit object 'exception' being equal = to null). Here is the (very ordinary) error page declaration line in the data = manipulation JSP: <%@ page errorPage=3D"AdderError.jsp" %> Here is the (equally ordinary) associated line in the JSP error page: <%@ page isErrorPage=3D"true" %> The only changes that have taken place since I last tested these pages = are the replacement of Java SDK1.4.2 with SDK1.5.0/5.0 and the replacement of Tomcat 4.1 with Tomcat 5.0. It seems highly unlikely that the change of SDK could have led to this = problem, but I suppose that there may be some change to Tomcat (or, more likely, version 2.4 of the servlet API) that has passed = me by. Can anybody shed light on the cause of this change in behaviour? Any assistance would be greatly appreciated. Cheers. Jan --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-user-help@jakarta.apache.org