Re: LookupDispatchAction problem with double byte resource files - working with DisplayTag ?
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 - have fun! And, good luck with this. Jack On Sat, 30 Oct 2004 18:49:33 -0700 (PDT), lixin chu <[EMAIL PROTECTED]> wrote: > 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 as well. > > it seems that i can not simply use myAction.dispatch > way to indicate which method I need and decouple the > label/action at the same time. > but your code certainly inspires me a lot. i am still > working on this now. > > thanks a lot. > > > li xin > > --- Dakota Jack <[EMAIL PROTECTED]> wrote: > > > 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 mapping. That is, the following code should > > be deleted. > > > > > > ... > > > > ... > > > > > > Second, the code > > > > > property="ListPermission.dispatch" value="done"> > > > > > > > > is right only if you are trying to use a method > > called > > "ListPermission". If you are trying to use a method > > called "done" > > with an action called "ListPermission", then this > > code should be: > > > > >property='done.dispatch"> > > > > > > > > This will result in the following parameters, for > > example, being in > > the request: done.dispatch.x=9 and > > done.dispatch.y=37. > > > > You are making things too complex. The solution > > simply needs whatever > > action [myAction' you want to be the value of the > > property attribute > > with ".dispatch" as a suffix, e.g. > > property=myAction.suffix. > > > > Jack > > > > > > On Sat, 30 Oct 2004 05:18:41 -0700 (PDT), lixin chu > > <[EMAIL PROTECTED]> wrote: > > > problem solved - I made a mistake in the JSP file, > > > here is the right one to return a parameter for a > > > submit button: > > > > > property="ListPermission.dispatch" > > value="done"> > > > > > > > > > > > > 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. Thanks Jack !!! > > > > > > li xin > > > > > > > > > > > > > > > --- lixin chu <[EMAIL PROTECTED]> wrote: > > > > > > > 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 parameter. > > > > > > > > So I tried to use a class specific parameter > > > > (together > > > > with the parameter used in Action mapping). This > > > > solves action chaining but them I got the submit > > > > button problem: > > > > > > > > here is my jsp file: > > > > > > > property="ListPermission.dispatch=done"> > > > > > > > > > > > > > > > > here is the partial action mapping: > > > > > > > > ... > > > > > > > > ... > > > > > > > > > > > > the intersting thing is that when the 'Done' > > button > > > > is > > > > clicked, the property is not passed in as > > parameter. > > > > I > > > > am lost. do not know why it is like this. > > > > > > > > anyway, thank you very much for your code and > > > > anwser. > > > > > > > > li xin > > > > > > > > > > > > > > > > --- Dakota Jack <[EMAIL PROTECTED]> wrote: > > > > > > > > > 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. I don't have > > time > > > > > to look at it in > > > > > further detail at this time. > > > > > > > > > > Jack > > > > > > > > > > On Fri, 29 Oct 2004 19:46:53 -0700 (PDT), > > lixin > > > > chu > > > > > <[EMAIL PROTECTED]> wrote: > > > > > > 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 m
Re: LookupDispatchAction problem with double byte resource files - working with DisplayTag ?
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 as well. it seems that i can not simply use myAction.dispatch way to indicate which method I need and decouple the label/action at the same time. but your code certainly inspires me a lot. i am still working on this now. thanks a lot. li xin --- Dakota Jack <[EMAIL PROTECTED]> wrote: > 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 mapping. That is, the following code should > be deleted. > > > ... > > ... > > > Second, the code > >property="ListPermission.dispatch" value="done"> > > > > is right only if you are trying to use a method > called > "ListPermission". If you are trying to use a method > called "done" > with an action called "ListPermission", then this > code should be: > > property='done.dispatch"> > > > > This will result in the following parameters, for > example, being in > the request: done.dispatch.x=9 and > done.dispatch.y=37. > > You are making things too complex. The solution > simply needs whatever > action [myAction' you want to be the value of the > property attribute > with ".dispatch" as a suffix, e.g. > property=myAction.suffix. > > Jack > > > On Sat, 30 Oct 2004 05:18:41 -0700 (PDT), lixin chu > <[EMAIL PROTECTED]> wrote: > > problem solved - I made a mistake in the JSP file, > > here is the right one to return a parameter for a > > submit button: > > > property="ListPermission.dispatch" > value="done"> > > > > > > > > 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. Thanks Jack !!! > > > > li xin > > > > > > > > > > --- lixin chu <[EMAIL PROTECTED]> wrote: > > > > > 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 parameter. > > > > > > So I tried to use a class specific parameter > > > (together > > > with the parameter used in Action mapping). This > > > solves action chaining but them I got the submit > > > button problem: > > > > > > here is my jsp file: > > > > > property="ListPermission.dispatch=done"> > > > > > > > > > > > > here is the partial action mapping: > > > > > > ... > > > > > > ... > > > > > > > > > the intersting thing is that when the 'Done' > button > > > is > > > clicked, the property is not passed in as > parameter. > > > I > > > am lost. do not know why it is like this. > > > > > > anyway, thank you very much for your code and > > > anwser. > > > > > > li xin > > > > > > > > > > > > --- Dakota Jack <[EMAIL PROTECTED]> wrote: > > > > > > > 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. I don't have > time > > > > to look at it in > > > > further detail at this time. > > > > > > > > Jack > > > > > > > > On Fri, 29 Oct 2004 19:46:53 -0700 (PDT), > lixin > > > chu > > > > <[EMAIL PROTECTED]> wrote: > > > > > 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 'Search Template' page, which > gets > > > the > > > > > search criteria and then pass the results to > the > > > > > ListTemplate.jsp page after pressing the > Search > > > > button > > > > > (it is associated with the 'search.dispatch' > > > > > parameter). The 'list parameter' page has a > > > > sortable > > > > > table (i am using DisplayTag): > > > > > > > > > > > > > > > > > > >pagesize="10" > > > > >id="templates" > > > > >sort="list" export="true" > > > > >requestURI="/Canal/admin/ListTemplate.do?
Re: LookupDispatchAction problem with double byte resource files - working with DisplayTag ?
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 mapping. That is, the following code should be deleted. ... ... Second, the code is right only if you are trying to use a method called "ListPermission". If you are trying to use a method called "done" with an action called "ListPermission", then this code should be: This will result in the following parameters, for example, being in the request: done.dispatch.x=9 and done.dispatch.y=37. You are making things too complex. The solution simply needs whatever action [myAction' you want to be the value of the property attribute with ".dispatch" as a suffix, e.g. property=myAction.suffix. Jack On Sat, 30 Oct 2004 05:18:41 -0700 (PDT), lixin chu <[EMAIL PROTECTED]> wrote: > problem solved - I made a mistake in the JSP file, > here is the right one to return a parameter for a > submit button: >property="ListPermission.dispatch" value="done"> > > > > 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. Thanks Jack !!! > > li xin > > > > > --- lixin chu <[EMAIL PROTECTED]> wrote: > > > 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 parameter. > > > > So I tried to use a class specific parameter > > (together > > with the parameter used in Action mapping). This > > solves action chaining but them I got the submit > > button problem: > > > > here is my jsp file: > > > property="ListPermission.dispatch=done"> > > > > > > > > here is the partial action mapping: > > > > ... > > > > ... > > > > > > the intersting thing is that when the 'Done' button > > is > > clicked, the property is not passed in as parameter. > > I > > am lost. do not know why it is like this. > > > > anyway, thank you very much for your code and > > anwser. > > > > li xin > > > > > > > > --- Dakota Jack <[EMAIL PROTECTED]> wrote: > > > > > 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. I don't have time > > > to look at it in > > > further detail at this time. > > > > > > Jack > > > > > > On Fri, 29 Oct 2004 19:46:53 -0700 (PDT), lixin > > chu > > > <[EMAIL PROTECTED]> wrote: > > > > 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 'Search Template' page, which gets > > the > > > > search criteria and then pass the results to the > > > > ListTemplate.jsp page after pressing the Search > > > button > > > > (it is associated with the 'search.dispatch' > > > > parameter). The 'list parameter' page has a > > > sortable > > > > table (i am using DisplayTag): > > > > > > > > > > > > > > >pagesize="10" > > > >id="templates" > > > >sort="list" export="true" > > > >requestURI="/Canal/admin/ListTemplate.do? > > > >sort.dispatch"> > > > > > > > > > name="basic.empty.showtable" > > > > value="true"/> > > > > > > > > > > > name="value( > > name="templates" > > > > property="id"/>)" value="x"/> > > > > > > > > > > > sortable="true" > > > > > > > href="TemplateManager.do?prepare.dispatch" > > > >paramId="templateID" > > > paramProperty="id"/> > > > > > > >property="category.name" > > > sortable="true" > > > > > > > href="TemplateManager.do?prepare.dispatch" > > > >paramId="templateID" > > > paramProperty="id"/> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > the problem is that the additional > > > > search.dispatch=Search is inserted into the > > > requestURI > > > > when I 'view source'. I have no idea. > > > > > > > > I am not sure if it is the DisplayTag limitation > > > > though ... > > > > > > > > thanks > > > > li xin > > > > > > > > --- Dakota Jack <[EMAIL PROTECTED]
Re: LookupDispatchAction problem with double byte resource files - working with DisplayTag ?
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. Thanks Jack !!! li xin --- lixin chu <[EMAIL PROTECTED]> wrote: > 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 parameter. > > So I tried to use a class specific parameter > (together > with the parameter used in Action mapping). This > solves action chaining but them I got the submit > button problem: > > here is my jsp file: > property="ListPermission.dispatch=done"> > > > > here is the partial action mapping: > > ... > > ... > > > the intersting thing is that when the 'Done' button > is > clicked, the property is not passed in as parameter. > I > am lost. do not know why it is like this. > > anyway, thank you very much for your code and > anwser. > > li xin > > > > --- Dakota Jack <[EMAIL PROTECTED]> wrote: > > > 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. I don't have time > > to look at it in > > further detail at this time. > > > > Jack > > > > On Fri, 29 Oct 2004 19:46:53 -0700 (PDT), lixin > chu > > <[EMAIL PROTECTED]> wrote: > > > 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 'Search Template' page, which gets > the > > > search criteria and then pass the results to the > > > ListTemplate.jsp page after pressing the Search > > button > > > (it is associated with the 'search.dispatch' > > > parameter). The 'list parameter' page has a > > sortable > > > table (i am using DisplayTag): > > > > > > > > > > >pagesize="10" > > >id="templates" > > >sort="list" export="true" > > >requestURI="/Canal/admin/ListTemplate.do? > > >sort.dispatch"> > > > > > > name="basic.empty.showtable" > > > value="true"/> > > > > > > > > name="value( > name="templates" > > > property="id"/>)" value="x"/> > > > > > > > > sortable="true" > > > > > href="TemplateManager.do?prepare.dispatch" > > >paramId="templateID" > > paramProperty="id"/> > > > > >property="category.name" > > sortable="true" > > > > > href="TemplateManager.do?prepare.dispatch" > > >paramId="templateID" > > paramProperty="id"/> > > > > > > > > > > > > > > > > > > > > > > > > > > > the problem is that the additional > > > search.dispatch=Search is inserted into the > > requestURI > > > when I 'view source'. I have no idea. > > > > > > I am not sure if it is the DisplayTag limitation > > > though ... > > > > > > thanks > > > li xin > > > > > > --- Dakota Jack <[EMAIL PROTECTED]> wrote: > > > > > > > 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 better alternatives in > various > > > > places. Some of them > > > > are itemized at > > > > http://www.michaelmcgrady.com/button/ . > > > > > > > > Jack > > > > > > > > > > > > On Wed, 27 Oct 2004 22:17:56 -0600, Kumar V > > Kadiyala > > > > <[EMAIL PROTECTED]> wrote: > > > > > 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 the > > > > > following message in the log. > > > > > [10/27/04 21:40:39:631 MDT] 67f967f9 > > DispatchActio > > > > E > > > > > org.apache.struts.actions.DispatchAction > > > > Request[/tag] does not contain > > > > > handler parameter name
Re: LookupDispatchAction problem with double byte resource files - working with DisplayTag ?
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 parameter. So I tried to use a class specific parameter (together with the parameter used in Action mapping). This solves action chaining but them I got the submit button problem: here is my jsp file: here is the partial action mapping: ... ... the intersting thing is that when the 'Done' button is clicked, the property is not passed in as parameter. I am lost. do not know why it is like this. anyway, thank you very much for your code and anwser. li xin --- Dakota Jack <[EMAIL PROTECTED]> wrote: > 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. I don't have time > to look at it in > further detail at this time. > > Jack > > On Fri, 29 Oct 2004 19:46:53 -0700 (PDT), lixin chu > <[EMAIL PROTECTED]> wrote: > > 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 'Search Template' page, which gets the > > search criteria and then pass the results to the > > ListTemplate.jsp page after pressing the Search > button > > (it is associated with the 'search.dispatch' > > parameter). The 'list parameter' page has a > sortable > > table (i am using DisplayTag): > > > > > > >pagesize="10" > >id="templates" > >sort="list" export="true" > >requestURI="/Canal/admin/ListTemplate.do? > >sort.dispatch"> > > > > > value="true"/> > > > > > name="value( name="templates" > > property="id"/>)" value="x"/> > > > > > sortable="true" > > > href="TemplateManager.do?prepare.dispatch" > >paramId="templateID" > paramProperty="id"/> > > >property="category.name" > sortable="true" > > > href="TemplateManager.do?prepare.dispatch" > >paramId="templateID" > paramProperty="id"/> > > > > > > > > > > > > > > > > > > the problem is that the additional > > search.dispatch=Search is inserted into the > requestURI > > when I 'view source'. I have no idea. > > > > I am not sure if it is the DisplayTag limitation > > though ... > > > > thanks > > li xin > > > > --- Dakota Jack <[EMAIL PROTECTED]> wrote: > > > > > 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 better alternatives in various > > > places. Some of them > > > are itemized at > > > http://www.michaelmcgrady.com/button/ . > > > > > > Jack > > > > > > > > > On Wed, 27 Oct 2004 22:17:56 -0600, Kumar V > Kadiyala > > > <[EMAIL PROTECTED]> wrote: > > > > 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 the > > > > following message in the log. > > > > [10/27/04 21:40:39:631 MDT] 67f967f9 > DispatchActio > > > E > > > > org.apache.struts.actions.DispatchAction > > > Request[/tag] does not contain > > > > handler parameter named method > > > > > > > > The Korean .properties was converted to ascii > > > (using nativetoascii) from > > > > its native encoding. Does this have to do > anything > > > with what I'm noticing? > > > > Should something additional be done when > > > .properties files are coverted to > > > > ascii? > > > > > > > > Help appreciated, > > > > Kumar > > > > > > > > > > > > > -- > > > "You can't wake a person who is pretending to be > > > asleep." > > > > > > ~Native Proverb~ > > > > > > "Each man is good in His sight. It is not > necessary > > > for eagles to be crows." > > > > > > ~Hunkesni (Sitting Bull), Hunkpapa Sioux~ > > > > > > > > > - > > > To unsubscribe, e-mail: > > > [EMAIL PROTECTED] > > > For additional commands, e-
Re: LookupDispatchAction problem with double byte resource files - working with DisplayTag ?
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. I don't have time to look at it in further detail at this time. Jack On Fri, 29 Oct 2004 19:46:53 -0700 (PDT), lixin chu <[EMAIL PROTECTED]> wrote: > 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 'Search Template' page, which gets the > search criteria and then pass the results to the > ListTemplate.jsp page after pressing the Search button > (it is associated with the 'search.dispatch' > parameter). The 'list parameter' page has a sortable > table (i am using DisplayTag): > > > pagesize="10" >id="templates" >sort="list" export="true" >requestURI="/Canal/admin/ListTemplate.do? >sort.dispatch"> > > value="true"/> > > name="value( property="id"/>)" value="x"/> > > sortable="true" >href="TemplateManager.do?prepare.dispatch" >paramId="templateID" paramProperty="id"/> >property="category.name" sortable="true" >href="TemplateManager.do?prepare.dispatch" >paramId="templateID" paramProperty="id"/> > > > > > > > > > the problem is that the additional > search.dispatch=Search is inserted into the requestURI > when I 'view source'. I have no idea. > > I am not sure if it is the DisplayTag limitation > though ... > > thanks > li xin > > --- Dakota Jack <[EMAIL PROTECTED]> wrote: > > > 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 better alternatives in various > > places. Some of them > > are itemized at > > http://www.michaelmcgrady.com/button/ . > > > > Jack > > > > > > On Wed, 27 Oct 2004 22:17:56 -0600, Kumar V Kadiyala > > <[EMAIL PROTECTED]> wrote: > > > 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 the > > > following message in the log. > > > [10/27/04 21:40:39:631 MDT] 67f967f9 DispatchActio > > E > > > org.apache.struts.actions.DispatchAction > > Request[/tag] does not contain > > > handler parameter named method > > > > > > The Korean .properties was converted to ascii > > (using nativetoascii) from > > > its native encoding. Does this have to do anything > > with what I'm noticing? > > > Should something additional be done when > > .properties files are coverted to > > > ascii? > > > > > > Help appreciated, > > > Kumar > > > > > > > > > -- > > "You can't wake a person who is pretending to be > > asleep." > > > > ~Native Proverb~ > > > > "Each man is good in His sight. It is not necessary > > for eagles to be crows." > > > > ~Hunkesni (Sitting Bull), Hunkpapa Sioux~ > > > > > - > > To unsubscribe, e-mail: > > [EMAIL PROTECTED] > > For additional commands, e-mail: > > [EMAIL PROTECTED] > > > > > > __ > Do you Yahoo!? > Yahoo! Mail - Helps protect you from nasty viruses. > http://promotions.yahoo.com/new_mail > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- "You can't wake a person who is pretending to be asleep." ~Native Proverb~ "Each man is good in His sight. It is not necessary for eagles to be crows." ~Hunkesni (Sitting Bull), Hunkpapa Sioux~ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: LookupDispatchAction problem with double byte resource files - working with DisplayTag ?
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 other dispatch action in struts whose name I have forgotten. Anyway, with that you don't need the parameter value or to use struts-config at all, except for other issues with respect to action mapping. Jack On Fri, 29 Oct 2004 19:46:53 -0700 (PDT), lixin chu <[EMAIL PROTECTED]> wrote: > 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 'Search Template' page, which gets the > search criteria and then pass the results to the > ListTemplate.jsp page after pressing the Search button > (it is associated with the 'search.dispatch' > parameter). The 'list parameter' page has a sortable > table (i am using DisplayTag): > > > pagesize="10" >id="templates" >sort="list" export="true" >requestURI="/Canal/admin/ListTemplate.do? >sort.dispatch"> > > value="true"/> > > name="value( property="id"/>)" value="x"/> > > sortable="true" >href="TemplateManager.do?prepare.dispatch" >paramId="templateID" paramProperty="id"/> >property="category.name" sortable="true" >href="TemplateManager.do?prepare.dispatch" >paramId="templateID" paramProperty="id"/> > > > > > > > > > the problem is that the additional > search.dispatch=Search is inserted into the requestURI > when I 'view source'. I have no idea. > > I am not sure if it is the DisplayTag limitation > though ... > > thanks > li xin > > --- Dakota Jack <[EMAIL PROTECTED]> wrote: > > > 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 better alternatives in various > > places. Some of them > > are itemized at > > http://www.michaelmcgrady.com/button/ . > > > > Jack > > > > > > On Wed, 27 Oct 2004 22:17:56 -0600, Kumar V Kadiyala > > <[EMAIL PROTECTED]> wrote: > > > 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 the > > > following message in the log. > > > [10/27/04 21:40:39:631 MDT] 67f967f9 DispatchActio > > E > > > org.apache.struts.actions.DispatchAction > > Request[/tag] does not contain > > > handler parameter named method > > > > > > The Korean .properties was converted to ascii > > (using nativetoascii) from > > > its native encoding. Does this have to do anything > > with what I'm noticing? > > > Should something additional be done when > > .properties files are coverted to > > > ascii? > > > > > > Help appreciated, > > > Kumar > > > > > > > > > -- > > "You can't wake a person who is pretending to be > > asleep." > > > > ~Native Proverb~ > > > > "Each man is good in His sight. It is not necessary > > for eagles to be crows." > > > > ~Hunkesni (Sitting Bull), Hunkpapa Sioux~ > > > > > - > > To unsubscribe, e-mail: > > [EMAIL PROTECTED] > > For additional commands, e-mail: > > [EMAIL PROTECTED] > > > > > > __ > Do you Yahoo!? > Yahoo! Mail - Helps protect you from nasty viruses. > http://promotions.yahoo.com/new_mail > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- "You can't wake a person who is pretending to be asleep." ~Native Proverb~ "Each man is good in His sight. It is not necessary for eagles to be crows." ~Hunkesni (Sitting Bull), Hunkpapa Sioux~ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: LookupDispatchAction problem with double byte resource files - working with DisplayTag ?
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 'Search Template' page, which gets the search criteria and then pass the results to the ListTemplate.jsp page after pressing the Search button (it is associated with the 'search.dispatch' parameter). The 'list parameter' page has a sortable table (i am using DisplayTag): )" value="x"/> the problem is that the additional search.dispatch=Search is inserted into the requestURI when I 'view source'. I have no idea. I am not sure if it is the DisplayTag limitation though ... thanks li xin --- Dakota Jack <[EMAIL PROTECTED]> wrote: > 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 better alternatives in various > places. Some of them > are itemized at > http://www.michaelmcgrady.com/button/ . > > Jack > > > On Wed, 27 Oct 2004 22:17:56 -0600, Kumar V Kadiyala > <[EMAIL PROTECTED]> wrote: > > 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 the > > following message in the log. > > [10/27/04 21:40:39:631 MDT] 67f967f9 DispatchActio > E > > org.apache.struts.actions.DispatchAction > Request[/tag] does not contain > > handler parameter named method > > > > The Korean .properties was converted to ascii > (using nativetoascii) from > > its native encoding. Does this have to do anything > with what I'm noticing? > > Should something additional be done when > .properties files are coverted to > > ascii? > > > > Help appreciated, > > Kumar > > > > > -- > "You can't wake a person who is pretending to be > asleep." > > ~Native Proverb~ > > "Each man is good in His sight. It is not necessary > for eagles to be crows." > > ~Hunkesni (Sitting Bull), Hunkpapa Sioux~ > > - > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > > __ Do you Yahoo!? Yahoo! Mail - Helps protect you from nasty viruses. http://promotions.yahoo.com/new_mail - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
