On 2/7/06, Paul Benedict <[EMAIL PROTECTED]> wrote: > I'd like to hear some feedback on an enhancement of MappingDispatchAction > (ParameterMappingDispatchAction) which I have contributed. It merges the > flexibility of choosing the dispatch through the request plus the static > configuration of which methods can be invoked. > > I've used this very successfully myself -- mainly for forms with many > buttons like a wizard form. This was inspired by Tapestry because not only > does Tapestry allow certain buttons to dictate which method to be called, > but sometimes no button is submitted at all (the enter key in IE) and a > default is selected. > > http://issues.apache.org/bugzilla/show_bug.cgi?id=38343 > > My testing was in Struts 1.2.8 and is targeting 1.2.x branch. If someone > needs be to write a test case, I will -- but please explain how I should do > it. I am use to non-http junit testing. If you want something more complex, > I will require some direction.
Hi Paul, I am going to try it today, but I already like it! Here is why: * one mapping can be used for several/all events for a particular action; * easy obfuscating; * Less stuff to iterate over, only method names in the mapping. The request values are verified directly, without iterating over all request parameters. * It is compact for what it does. * No changes to config file. Good job! Michael. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
