Re: Handling Exceptions in ActionForm

At your own risk, manipulate the ActionErrors and ActionMessages collections any way you like. They're in the request scope and named according to Globals.ERROR_KEY and Globals.MESSAGE_KEY. m --- Shane Mingins [EMAIL PROTECTED] wrote: Hi I have a Swing app where the SwingView implements

RE: Handling Exceptions in ActionForm

-Original Message- From: Shane Mingins [mailto:[EMAIL PROTECTED] Using Struts, if I have an ActionForm implement the view interface, how would it create an ActionError or ActionMessage? It seems that from an ActionForm the validate() method can do it, and an Action can do it

RE: Handling Exceptions

For ServletException, configure the error page in web.xml file. it will work. navjot |-Original Message- |From: Mohd Amin Mohd Din [mailto:[EMAIL PROTECTED] |Sent: Sunday, August 31, 2003 5:12 PM |To: [EMAIL PROTECTED] |Subject: Handling Exceptions | | |Hi, | |In struts-config, I have

Re: Handling Exceptions

However, when a ServletException occurs, it does not go to the path defined in struts-config.xml. Somehow, the error is still showing in the application page and not in any one of the error pages defined. My guess is, the ServletException is happening someplace where Struts' ExceptionHandler

Re: Handling Exceptions

You should probably create a global exception handler in your Struts configuration file. Something like this: global-exceptions exception key=global.error.internal path=/ErrorPage.jsp scope=request type=java.lang.Exception/ /global-exceptions hope this helps --Alen -

Re: Handling exceptions in Action class

Take a look at my draft chapter on ExceptionException and see if that sheds any light on the topic. You can download it here: http://www.theserverside.com/resources/strutsreview.jsp It's Chapter 10. You will need to register, but it's free. Chuck Hi all: Can anyone kindly suggest, if i

RE: Handling exceptions

., when we end up in the catch Throwable block in validate() or in perform(). Hani. -Original Message- From: Dariusz Wojtas [mailto:[EMAIL PROTECTED]] Sent: Monday, March 04, 2002 4:06 PM To: Struts Users Mailing List Subject: RE: Handling exceptions OK, that was helpful - now I see it from

RE: Handling exceptions

Catching Throwable will catch both Exceptions and Errors. Catching Exception will only catch Exceptions. You will want to catch Exceptions *AND* Errors to be bullet-proof. We were catching Exception for a while and we thought we were covered, until one day we got (due to some weird deployment) a

RE: Handling exceptions

OK, that was helpful - now I see it from different perspective. But what if somebody argues that Throwable catches also JVM exceptions, like ThreadDeath or OutOfMemory and similar? Should I care about that or not? If not then why? Dariusz Wojtas At 13:14 02-03-04 -0500, you wrote:

Re: handling exceptions

We've developed a pretty eloborate exception handling framework on my current project. We're using EJB on the backend, so we must also deal with remote type exceptions. First we catorgize exceptions into those that the user can recover from and those that they can't. Sort of like fatal and

RE: handling exceptions

How do you differentiate between these exceptions (throws, throw new, catch) in the JavaDocs? Mark -Original Message- From: Chuck Cavaness [mailto:[EMAIL PROTECTED]] Sent: Monday, January 28, 2002 7:27 AM To: Struts Users Mailing List Subject: Re: handling exceptions We've developed

Re: Handling exceptions thrown from Action.perform in the errorpage?

global-forwards forward name=errorpath=/errorpage.jsp/ /global-forwards return mapping.findForward(error) Will forward to the file named errorpage.jsp in the root of your Web application. If it doesn't, something else is wrong, like doPerform is not throwing the