Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 88666 invoked from network); 3 Feb 2003 13:43:41 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 3 Feb 2003 13:43:41 -0000 Received: (qmail 11183 invoked by uid 97); 3 Feb 2003 13:45:08 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@nagoya.betaversion.org Received: (qmail 11176 invoked from network); 3 Feb 2003 13:45:07 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by nagoya.betaversion.org with SMTP; 3 Feb 2003 13:45:07 -0000 Received: (qmail 86599 invoked by uid 500); 3 Feb 2003 13:42:55 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 86569 invoked from network); 3 Feb 2003 13:42:54 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 3 Feb 2003 13:42:54 -0000 Received: (qmail 11123 invoked by uid 50); 3 Feb 2003 13:44:21 -0000 Date: 3 Feb 2003 13:44:21 -0000 Message-ID: <20030203134421.11122.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: tomcat-dev@jakarta.apache.org Cc: Subject: DO NOT REPLY [Bug 16701] New: - No exception if jsp:include fails X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . 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=16701 No exception if jsp:include fails Summary: No exception if jsp:include fails Product: Tomcat 4 Version: 4.1.12 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority: Other Component: Jasper AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: g.sauer-limbach@vcontarget.de If the standard action jsp:include fails to locate the resource (say JSP file) specified in the page attribute, there is no exception generated. Tomcat does just do nothing about the failed include action, but leaves the place in the response empty. Tomcat 3.2 did throw a java.io.FileNotFoundException, which I would also expect to obtaine using Tomcat 4.1. I did not try other versions of Tomcat 4, but two different installations of Tomcat, one 4.1.12, antoher 4.1.x had the same problem. I checked not to be confused by the ErrorPage (removing the part in the page directive), also put try/catch around the include with various exception classes; none showed any evidence of an exception thrown by the code executing the jsp:include action. Using pageContext.include() behaves the same. jsp:includes does work well if the page can be found. --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org