OK - I'll say again - it IS optional AND explicit :)
(One way to make it more explicit is make execute() final in AS?)
I definitely agree with liberal use of 'final' and 'abstract'. By all means please use final whenever it would be silly to override a method.
I maintain that 95% of web actions are neatest when done with 3-phase
support - it's what we use most in almost all our apps! Are we just that
different to the rest of the world? How do y'all do it? (Maybe that will
help me come to terms with removing it)
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.
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
