You're making the assumption that everyone wants to do things the way you do - SimpleDispatchAction doesn't replace any of them if people don't. Personally (if I used them :-)) MappingDispatchAction looks good to me for most use cases or if I didn't want to specify anything in the struts-config.xml then have a custom DispatchAction that just always used "method" as the parameter name to find the method name from the request.
Niall ----- Original Message ----- From: "Michael McGrady" <[EMAIL PROTECTED]> To: "Struts Developers List" <[EMAIL PROTECTED]> Sent: Friday, September 17, 2004 12:40 AM Subject: Re: DispatchAction > Tom Drake wrote: > > >It appears that what we have are different strategies for determining the > >method name. > > > > Yes! *_/The existing classes use DIFFERENT DATA AND DIFFERENT LOGIC to > get the method name/_*. The ONLY thing SimpleDispatchAction and the > present classes have in common is that they do get the method name and > that they use reflection once they have the method name. The present > classes use a combination of a request parameter value from a name/value > pair with the value of an ActionMapping parameter property to determine > the method. SimpleDispatchAction uses neither of these sources and so, > requires no special coding in struts-config.xml and frees up the related > values for the name/value pairs in <a href=>, <input type='submit'>, > <input type='image> and <input type='file> for whatever clever > machinations we coders can create. > > The SimpleDispatchAction, if it were not for legacy uses, can completely > replace the three existing dispatch classes. > > Enough from me. I am too noisy. Right? > > Michael McGrady > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
