[S2.1] Change to actionMessage and actionError handling

[Al Sutton <al...@alsutton.com>]

Guys,

One of the things that really gets me is the loss of action messages and 
errors when using anything other than the default result type. imho given 
that post and redirect is probably the most common pattern for form handling 
we should allow messages to be passed on via the post-POST redirect as part 
of the default configuration.

What do other people think?

Al. 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org

Re: [S2.1] Change to actionMessage and actionError handling

[Brian Pontarelli <br...@pontarelli.com>]

Al Sutton wrote:
> Guys,
>
> One of the things that really gets me is the loss of action messages 
> and errors when using anything other than the default result type. 
> imho given that post and redirect is probably the most common pattern 
> for form handling we should allow messages to be passed on via the 
> post-POST redirect as part of the default configuration.
>
> What do other people think?
Just having this same thought last night and took another look at the 
scope plugin. I think there are a number of places that we can improve 
on with errors, validation, etc in addition to scopes. The current 
ValidationAware subclasses make it difficult to manage scopes and the 
validation interceptor can be tricky unless you are really knowledgeable 
about what it does exactly.

It seems like validation should get an API make-over and scopes dropped 
into core.

-bp

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org