Rick Reumann wrote the following on 7/22/2005 1:33 PM:
onclick="myForm.dispatch.value='someDispatchMethod'"
You can use this kind of code with almost anything (with images just
also add myForm.submit()). Easy to use and no need to figuure out how
yet another flavor of SomeonesNewAndImprovedAction works.
To further add, I'm not saying I don't like these other solutions, but I
like consistency. To me it's very easy for a developer to see a
"dispatch" hidden variable on a page and quickly see how it might
possibly be being set.
When you start adding alternative ways to have your disaptch method
called, it becomes more confusing to try and figure out what actually
gets called. This was a big beef I had with LookUpDispatchAction... it
was so annoying to figure what button did what.. it was complicated by
the fact that it's a good idea to use the ApplicationResources for the
names of your buttons. Yet, think how annoying it is to figure out what
happens... you have to look at the button, the app resources file, then
a map in the Action, and then finally you can figure out what method
gets called. I'm not saying these other solutions work this way (I know
they don't), but I'm just making the point that I find it nice to have
one consistent way of doing things that's easy for other developers to
follow.
--
Rick
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
