Wendy, You raise an excellent point. I am going to retract my previous advice; it is obviously wrong.
A 500 error is a response code. If a response has not been committed to the stream, the application container can translate an exception into a 500 status code. However, if the response stream always has data flowing back (code 200) and then an exception occurs, there is no way to change the status: here an exception occurred within a successful response. David, It looks like you will need both the 500 error handler and the exception handler. The first for failures before the response, and the second for failures during the response. Thanks! -----Original Message----- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Thursday, May 26, 2005 3:21 PM To: Struts Users Mailing List; [EMAIL PROTECTED] Subject: Re: <error-page> not catching errors... From: "David Johnson" <[EMAIL PROTECTED]> > It's insane to me that this cant be done with Tomcat 4.1.31 > the Struts documents tell you to do exactly what I'm trying. > http://jakarta.apache.org/tomcat/faq/misc.html#error I think what you might be running into is that when you catch an error 500 by configuring something in web.xml, you're out in the container, and it doesn't know anything about Struts or Tiles. Try it with a plain jsp or html page, and it should work. (It does for me, on Tomcat 4.1.30.) -- Wendy Smoak --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ------------------------------------------------------------------------------ Notice: This e-mail message, together with any attachments, contains information of Merck & Co., Inc. (One Merck Drive, Whitehouse Station, New Jersey, USA 08889), and/or its affiliates (which may be known outside the United States as Merck Frosst, Merck Sharp & Dohme or MSD and in Japan, as Banyu) that may be confidential, proprietary copyrighted and/or legally privileged. It is intended solely for the use of the individual or entity named on this message. If you are not the intended recipient, and have received this message in error, please notify us immediately by reply e-mail and then delete it from your system. ------------------------------------------------------------------------------ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
