We will eventually, of course. For now, though, I wanted to setup a higher level error handling for those situations where we make a mistake and don't catch it or before we get thorough exception handling in place. That way the 500 errors get logged, but don't come back to the user with a stack trace.
Preston >>> [EMAIL PROTECTED] 10/5/2005 3:34:04 PM >>> Preston CRAWFORD wrote: >This actually does get me some of the information. Unfortunately since >I'm sticking another servlet (my action) in between, the exception acts >like it's coming from my action. So it appears I may have to go the >route of extending the ExceptionHandler. I was hoping there was a way to >avoid that, but it doesn't appear so. > > I'm still a bit confused about what you're trying to accomplish. Why not catch the exception in the Action (or wherever it's being generated) and log it from there rather than waiting down the line? Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
