I notice that your original question had to do with multiple submit
buttons, but that your code here only has one submit button. You
cannot necessarily take a solution for one problem and use if for
others. I don't know about the display tag, so I am not sure if you
are doing the right thing
problem solved - I made a mistake in the JSP file,
here is the right one to return a parameter for a
submit button:
html:submit
property=ListPermission.dispatch value=done
bean:message key=button.done/
/html:submit
So in this case, if the Done button is pressed,
Hello, Chu,
You seem to be a bit mixed up. I am not even sure which solution you
are using anymore. However, if you are using the solution at
www.michaelmcgrady.com/button we discussed, then you have this coded
wrong.
First, you should have nothing in the parameter attribute of your
action
Hi Jack,
you are right, it is indeed mixed up - all becuase I
need to support action chaining. So I had to modify
your code a bit 'cus it seems that the simple
MyAction.dispatch can not support my case.
secondly, I just realize that even my html:submit
code is wrong becuase 'value=xxx' will be
The code has nothing to do with myAction.dispatch. And, the code is
not mine. You have it all wrong: dispatch is not connected to the
action but to the html. There is nothing related to action chaining
inconsistent with any of the alternatives. I don't know what you've
done with the code, but
hi jack,
thanks, the solution is cool ! I am trying it.
a small problem i am experiencing now is that (i am
not sure if there is something wrong in my
configuration), the parameter on one page is passed on
to the next page, so when we getMethod, the earlier
method name is returned.
I have one
You do not have to use the parameter at all to do this. Just use the
name for the submit with .dispatch. Go back to the website I noted to
you and you will see. The DispatchAction there is a complete
substitute not for DispatchAction but for DispatchAction,
LookupDispatchAction and the other
7 matches
Mail list logo
