Return-Path: 
 <users-return-245588-apmail-tomcat-users-archive=tomcat.apache.org@tomcat.apache.org>
X-Original-To: apmail-tomcat-users-archive@www.apache.org
Delivered-To: apmail-tomcat-users-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 77DF2100F4
	for <apmail-tomcat-users-archive@www.apache.org>;
 Thu,  9 Jan 2014 19:29:15 +0000 (UTC)
Received: (qmail 50494 invoked by uid 500); 9 Jan 2014 19:29:03 -0000
Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org
Received: (qmail 50450 invoked by uid 500); 9 Jan 2014 19:29:02 -0000
Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@tomcat.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@tomcat.apache.org>
List-Post: <mailto:users@tomcat.apache.org>
List-Id: <users.tomcat.apache.org>
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Delivered-To: mailing list users@tomcat.apache.org
Received: (qmail 50432 invoked by uid 99); 9 Jan 2014 19:29:02 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Jan 2014 19:29:02 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of tomcat.random@gmail.com
 designates 209.85.214.178 as permitted sender)
Received: from [209.85.214.178] (HELO mail-ob0-f178.google.com)
 (209.85.214.178)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Jan 2014 19:28:55 +0000
Received: by mail-ob0-f178.google.com with SMTP id uz6so3725006obc.23
        for <users@tomcat.apache.org>; Thu, 09 Jan 2014 11:28:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=BVqgwf1Fcrb005Q0Yej4JsWeV2Bi0CRmKIN7QF930po=;
        b=upi+HHyDNVQmhCFYaxCCb5ZKHR7UtT10jLiDyTCLAMMNHXzN3uj/mOB7R6fC153Fxf
         Pk/9/9UBzmAZfmUb4+kmgenmu1YgrYEt7lzJ3Gsof2+8GMTL0h2i2gGHahs7o0LbrvBh
         7GXQ+F92Px4bS3bRO2RLeCe+g2NvDk4f+e1SVYX8ABwYMH+HRMySPzpi/79SU0yx4adX
         fJ3mZJYuOdua/b/5V+DosCcqceAeysnCM2lhW4K6Fq6JyxZiyUILvCCXoL0Lj5fQXCrK
         wrUfYxSVYID75/dNrz+Ve0HoJBDLqoPxlXpONHAA41ySs0E21FF9M/UnyVV0R4uQSAPt
         K0lw==
MIME-Version: 1.0
X-Received: by 10.60.62.199 with SMTP id a7mr2654436oes.64.1389295714917; Thu,
 09 Jan 2014 11:28:34 -0800 (PST)
Received: by 10.182.213.137 with HTTP; Thu, 9 Jan 2014 11:28:34 -0800 (PST)
Date: Thu, 9 Jan 2014 14:28:34 -0500
Message-ID: 
 <CAPhkb93ekWVUq3xxkbbCGjSHiR+=1C1WEnjCjHdYFpeMQ+zHxA@mail.gmail.com>
Subject: PropertyNotFoundException does not work with custom error in web.xml
From: Tomcat Random <tomcat.random@gmail.com>
To: Tomcat Users List <users@tomcat.apache.org>
Content-Type: multipart/alternative; boundary=001a11c2190c9363b704ef8e9d5f
X-Virus-Checked: Checked by ClamAV on apache.org

--001a11c2190c9363b704ef8e9d5f
Content-Type: text/plain; charset=ISO-8859-1

I have a custom error servlet set up in my webapps web.xml file like so:

<error-page>
        <exception-type>java.lang.RuntimeException</exception-type>
        <location>/runtimeExceptionHandler</location>
</error-page>

In JSTL if a property is spelled incorrectly or doesn't exist, the
PropertyNotFoundException will not trigger the error servlet, even though
PNFEs extend RuntimeException. Anyone know why this is?

Tomcat 7.037 on Win7.

TIA
Alec

--001a11c2190c9363b704ef8e9d5f--