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,
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
code is wrong becuase 'value=xxx' will be used as
label
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 mapp
problem solved - I made a mistake in the JSP file,
here is the right one to return a parameter for a
submit button:
So in this case, if the Done button is pressed,
'ListPermission.dispatch=done' is sent to the server.
So now I hope I have a complete decoupled, I18N aware
DispatchAction. Tha
I realize that the problem is action chaining.
In my code, action one goes on to the next action - I
persume that the parameters passed to the first action
are still passed on to the next. here the problem
comes in: new parameter is appended at end so
getMethodName always gets the earlier paramete
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 here
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 oth
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 'Se
All of your problems are caused because LookupDispatchAction creates a
reverse mapping from the value of a parameter to its key, in order to
get the method name. This is not only resource intensive but also a
constant source of the sorts of difficulties you are experiencing. You
can find what are
Hi all,
I'm using LookupDispatchAction to submit a form with multiple submit
buttons. The labels of the buttons are translated. The translated strings
are in a .properties file. I'm able to run the web app fine in English but
when I switch to Korean none of the the submit buttons work and I see
10 matches
Mail list logo
