> -----Original Message----- > From: Erik Hatcher [mailto:[EMAIL PROTECTED] > Sent: Wednesday, July 02, 2003 3:53 PM > To: [EMAIL PROTECTED] > Subject: Re: [OS-webwork] Default workflow > > > 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 >
The idea is just to make it optional and explicit... There have been a lot of people confused (repeatedly) about getting "input" returned without it even hitting your action... Especially if you're not even return "input" anywhere in your code and you didn't map a page for it! I must say I've fallen victim to this myself, so making this explicit should make you have to think about it. Jason ------------------------------------------------------- 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
