I believe the webapp catches it prior to that, Chuck. And FYI, I tried it with a space and without. You would think that I'd get a malformed XML error upon startup, wouldn't you? Well, I didn't.
-----Original Message----- From: Caldarale, Charles R [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 10, 2007 1:25 PM To: Tomcat Users List Subject: RE: customized error page for tomcat depending on code > From: Propes, Barry L [mailto:[EMAIL PROTECTED] > Subject: RE: customized error page for tomcat depending on code > > <error-page> > <exception-type>java.sql.SQLException.Exhausted ResultsSet</exception-type> > <location>/chngctrl/500error.jsp</location> > </error-page> You don't really have a space in the middle of a class name, do you? That obviously can't work. Does the exception make it all the way back to Tomcat? Or does the webapp catch it and prevent the container from ever seeing it? The stack trace associated with the exception should tell you. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
