Dave,
The problem is that if your action uses addActionError and returns INPUT
to get a redirect to another action the validation also uses teh input
result of the action you've been redirected to.
I agree that upon an error you want to go back to the input page, but if
your error is added in ActionB, and you're using an action as the input
page (ActionA), and you have the relevant interceptors enabled, the
current behaviour sends you to the input page of the input Action of the
action where the error was added (i.e. the input result of ActionA)
instead of just the input action of where the error occurred (i.e. the
input result of ActionB).
Al.
Dave Newton wrote:
--- Al Sutton <[EMAIL PROTECTED]> wrote:
at the moment there appears to be a bug in that if
you use addActionError, the message store
Interceptor, and you have the validation interceptor
enabled you will get redirected to the input result
of the action after the redirect :(
I'm not sure I'd classify that as a bug. The default
use case (IMO) is that if you have errors you want to
go back to the input page.
If you want to work around the default behavior then
take a look at the DefaultWorkflowInterceptor source
and create your own that does something different, or
use messages, which are not handled as errors are.
d.
____________________________________________________________________________________
Pinpoint customers who are looking for what you sell.
http://searchmarketing.yahoo.com/
---------------------------------------------------------------------
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]
