Well, the drawback is that now you need a hack interceptor to intercept attempts to misuse the dispatch action... Plus, the DispatchAction feels very... Struts :-)
Seriously, being able to specify the method to call in the action element is much more clear to me than setting a method param... This is in there for the same reason IoC is in Xwork. These are different styles of programming that have proven to be valuable, so they are supported in the core framework. If you have multiple buttons on a page that do different things, do you really want to have n different commands for it all extending from a common base class? There are other patterns of use that can be implemented with Interceptors and class hierarchies as well, and if they prove to be valuable, they'll be incorporated into the core framework as well. Jason > -----Original Message----- > From: Erik Hatcher [mailto:[EMAIL PROTECTED] > Sent: Wednesday, July 02, 2003 4:51 PM > To: [EMAIL PROTECTED] > Subject: Re: [OS-webwork] WebWork2, here I come! > > > On Wednesday, July 2, 2003, at 04:29 PM, Jason Carreira wrote: > > This is how WW1.x command driven actions are implemented. > What I don't > > like about this implementation is that anyone who know a little bit > > about how WW works can twiddle with URLs to call other > methods. Maybe > > not a huge risk, but just ugly. > > This could be prevented with a different interceptor than the > Parameter > one, or some other interceptor facility to keep ?method=xyz from > switching things. > > > People can choose not to use different methods on their > actions, but I > > want the ability to use it to keep from having a proliferation of > > Action classes. > > Its just one DispatchAction though. Where is the proliferation? > Subclass that and have at it with all the dynamic entry points you > want. I'm still not seeing the drawback to this for you. > > I think keeping the Action interface tight, yet allowing implementors > to do their own thing if they desire gives us the best of > both worlds. > Why should the framework itself accommodate this type of dynamic > dispatching for you? I'm still not sold. But I'm still > listening and > *learning*. > > 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_06 1203_01/01 _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork ------------------------------------------------------- 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
