> Have you read my exception handling chapter on > theserverside.com? If that doesn't answer this question, > than I've failed and I need to rewrite that chapter.
Thanks Chuck.. excellent stuff! I extended ExceptionHandler, and this did the trick. One small concern is that the DTD for struts-config.xml says that the "exception" element requires that the "key" attribute be specified. My ExceptionHandler doesn't use application.resources or ActionErrors at all, so the key is not required. Everything worked fine, but given this requirement, and given that storeException also requires ActionErrors, people might be under the assuption that the can't use Struts error handling without using ActionErrors. Thanks again, Roy > > > > I'm having a problem with exception handling with 1.1b. This problem > > has been brought up before > > (http://www.mail-archive.com/struts-user@jakarta.apache.org/msg29572.html) > > but never fully discussed. I can't see any way for my Action that deals > > with global-exceptions to get a handle to the Exception that was thrown, > > without creating my own ExceptionHandler class. > > > > Shouldn't all exceptions that are minor enough to use ActionErrors be caught > > within an Action and not thrown to a global-exception? imho, global > > exceptions should be for reporting major, unexpected exceptions. The Action > > that handles that exception should have a handle to an Exception object, not > > to an ActionError object. This way the proper reporting can be done > > (emailing of stack traces, etc.), and the user should recieve a generic > > error page. > > > > Any other thoughts on this? > > > > -Roy > > > > > > -- > > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
