that last part...if it's nothing more, which doesn't surprise me, then yeah, I'll need to come up with another solution outside of catching that particular 500 error within the server.xml file.
basically, Tomcat would catch it with the class name in there correctly, but would simply ignore it if I added something to it (like the specific root cause message - in this case Exhausted ResultSet. I think I can forge a different solution applicable to this, though. Thanks for clarification on the other...I won't waste one second more trying to "hammer a square peg in a round hole." -----Original Message----- From: Caldarale, Charles R [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 10, 2007 2:58 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 > > I believe the webapp catches it prior to that, Chuck. If the webapp catches the exception, then how could you expect Tomcat to process it? > 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? No, I wouldn't. Pretty much any string of Unicode characters is syntactically valid for most XML attributes; it's the semantics of the value that are important, and clearly, no class name should have a space in it (although, technically, spaces are allowed). Note that the value for an <exception-type> must be a class name, nothing more. There's no mechanism defined in the servlet spec to utilized attributes of an exception, which is what you're trying to do. If you have control of the webapp, you could have it catch that particular exception and then rethrow some unique type that could be declared in <exception-type>. - 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]
