While we're bringing up controversial topics....
I would like to undo this, pull the implementation stuff up into
ActionSupport, get rid of the workflow and BaseActionSupport, and create
a DefaultWorkflowInterceptor which will call validate() on the Action if
it implements an Interface, then check for errors like above and return
INPUT without forwarding to the rest of the interceptor stack if it has
errors, or forward to the rest of the interceptor stack if it does....
Probably you'd want to put this as the last interceptor in your stack,
so forwarding would just call the Action.
Sounds great! I was going to suggest something similar with the ValidationInterceptor. It was confusing that it called execute() (to me, coming from a Struts experience) when validations failed... and then I found ActionSupport that took care of it.
I'd prefer the validation automatically go back to INPUT, so if this isn't going to be available in a built-in interceptor I'd roll my own probably.
This may be completely out of line with what you're talking about, just sharing my thoughts/confusion on ValidationInterceptor.
Erik
------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork