Re: Basic validation, input, and redirects

I'll expand on this comment (and I believe this is what ravi_eze is suggesting)... I have a similar situation in my application, and I got around it by creating a non-validating stack for the "setup" actions. I basically removed all the interceptors that trigger validation for those actions where

Re: Basic validation, input, and redirects

i think u can ty this way: create a new mapping where there are no validations for action 1. Now on validation errors of action 2 it would redirect to this action 1; thus skipping validations of action 1. if u want the function call only and no validations... may b u can call the method action1

Re: Basic validation, input, and redirects

Thanks for the comment. The problem is not that I'm losing the validation errors. I'm keeping those across the redirect by using a modified interceptor stack with the STORE interceptor. So, that's cool. The problem is that *because* the errors are being preserved across the redirect (I

Re: Basic validation, input, and redirects

Kevin Wade wrote: Greetings. I've seen a number of posts about this issue -- or related issues -- but no comprehensive solution. I'll try again and be succinct: I have an action (Action1) that prepares a search screen (i.e. populates a drop-down box). The search screen/form calls Action2 bu