> From what I've seen of WW2 so far and comparing how I'd apply it > against our current Struts app, I'd still use Action/execute, perhaps > with my own base class to provide a thin layer of control. I'd use a > validating interceptor that kicked back INPUT without calling execute, > and I'd be able to (probably) do what we do with Struts easily. I > don't really need/want a base class that did more stuff. Inheritance > is the last thing I want to use, and it doesn't really seem necessary > to accomplish my use cases. With the interceptors (very nice, BTW!) I > could get away from having a thin layer base action class since I could > intercept to add before/after if need be.
That's exactly why we have BaseActionSupport which has just execute(), but gives you error messages and i18n. If you do want 3-phase support, you can use ActionSupport. M ------------------------------------------------------- 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
