Return-Path: Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 60397 invoked from network); 6 Feb 2001 00:53:57 -0000 Received: from patan.sun.com (192.18.98.43) by h31.sny.collab.net with SMTP; 6 Feb 2001 00:53:57 -0000 Received: from shorter.eng.sun.com ([129.144.250.35]) by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id QAA21874 for ; Mon, 5 Feb 2001 16:54:05 -0800 (PST) Received: from egmont (egmont [129.144.251.58]) by shorter.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.0) with SMTP id QAA13170 for ; Mon, 5 Feb 2001 16:54:04 -0800 (PST) Message-Id: <200102060054.QAA13170@shorter.eng.sun.com> Date: Mon, 5 Feb 2001 16:54:04 -0800 (PST) From: Danny Coward Reply-To: Danny Coward Subject: Re: RequestDispatcher and exceptions To: tomcat-dev@jakarta.apache.org MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: fi+9E0nqgcimPRp2uHHjmg== X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4 SunOS 5.8 sun4u sparc X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N >Section 8.5 in 2.3 PFD says: >"Only runtime exceptions and checked exceptions of type ServletException >and IOException should be propagated ... if thrown by the target of >RequestDispatcher. All other exceptions should be wrapped ... " > >My understanding of this is that NullPointerException should be >propagated, not wrapped, same for security and any other RuntimeException. Yes - and the same requirement is in the 2.2 version as well - that exceptions inheriting from RuntimeException should be popped up to the caller. - Danny