This looks useful, but would be even more so if you could include the following type
of exception mapping:
action
exception error=some.error.key
type=package.Exception /
/action
The action servlet would then generate an ActionError and add it to the
: Declarative exception handling for Action classes
This looks useful, but would be even more so if you could include the
following type
of exception mapping:
action
exception error=some.error.key
type=package.Exception /
/action
The action servlet would
I was presuming that the default behaviour would be for the ActionServlet to
send the user back to the 'input' page on error; but these would be useful
optional
parameters.
Laine: would you consider incorporating this, or should I have a go myself?
Deadman, Hal wrote:
Wouldn't Joe Faith's
10:12 AM
To: Struts Developers List
Subject: Re: Declarative exception handling for Action classes
I was presuming that the default behaviour would be for the
ActionServlet to
send the user back to the 'input' page on error; but these would be
useful
optional
parameters.
Laine: would you consider
I would love to have this feature.
-Original Message-
From: Joe Faith [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 01, 2001 7:12 AM
To: Struts Developers List
Subject: Re: Declarative exception handling for Action classes
I was presuming that the default behaviour would
I haven't tried the code, but assuming it works, I think I'm on board
here.
The part about perform() throwing Exception gives me pause though.
Does perform need to throw Exception, or does ActionController simply
need to catch Exception?
Why are EjbExceptions handled differently?
If this is
On Wed, 31 Oct 2001, Laine Donlan wrote:
Date: Wed, 31 Oct 2001 22:06:06 -0500
From: Laine Donlan [EMAIL PROTECTED]
Reply-To: Struts Developers List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Declarative exception handling for Action classes
Wanted to submit the following code
- If we pass the actual exception as attributes, I would suggest
using request scope rather than session scope. This will allow
the technique to work even in apps that don't use sessions, and
will also avoid problems when there are multiple simultaneous
requests for a particular
- As an alternative to passing the exception you are throwing under
a particular request or session scope key, how about having your
Action simply wrap the business logic exception inside a
ServletException (as the root cause) and throw that? The perform
method already declares
On Thu, 1 Nov 2001, Laine Donlan wrote:
Date: Thu, 1 Nov 2001 16:44:06 -0500
From: Laine Donlan [EMAIL PROTECTED]
Reply-To: Struts Developers List [EMAIL PROTECTED]
To: Struts Developers List [EMAIL PROTECTED]
Subject: RE: Declarative exception handling for Action classes
If we had thought of this when first designing Struts, that would have
made sense. But now, I would be ***really*** hesitant to change the
method signature for Action.perform() and potentially break everybody's
existing implementations.
I guess that makes perfect sense, wouldn't want to break
11 matches
Mail list logo
