Sorry if this is not helpful to you, Jim. However, I meant the opposite of what you are saying. I am saying that the computer is doing exactly what is coded and, so, the answer lies in tracking the output. I would never think that the impossible is possible or any other such philosophical drivel. Sorry I gave that impression. I am a preeminently practical person. That is what I mean when I say "the computer is always right'. Hopefully my next suggestion makes that clear. I think this is really a simple problem to solve if one merely debugs following the LookupDispatchAction code and determines where the wrong value appears. This is not a rocket science problem. That is my point.
Jack On Wed, 8 Dec 2004 09:09:46 -0700, Jim Barrows <[EMAIL PROTECTED]> wrote: > > > > > > -----Original Message----- > > From: Alexander Czernay [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, December 08, 2004 6:14 AM > > To: Struts Users Mailing List > > Subject: Re: LookupDispatchAction doesn't lookup mapping > > > > > > Dakota Jack wrote: > > > My experience is that the computer is always right, so I > > would look in > > > my properites file, if I were you, and see whether or not I had > > > reversed the myButtonForward=go to go=myButtonForward. Did you? I > > > feel compelled to reiterate that LookupDispatchAction is a > > fairly poor > > > example of the code needed to do this stuff, in my opinion. > > > > > > Jack > > > > > > > > > > I will definitely try your suggestion out, but before that, I > > wanted to > > figure out, what I had done wrong using the LookupDispatchAction. > > > > So now some direct copy & paste from my code. > > My ApplicationRessurces.properties looks like this: > > <snip> > > authors-form.button.forward = weiter > > authors-form.button.back = zurück > > </snip> > > > > The jsp: > > This suggestion comes under the heading "When only the impossible is left, > the impossible must be possible". I don't think this is it..... > Why do you have <html:form twice? You only need it once with either button. > It shouldn't matter, but everything else looks right, and exactly the way I > have it working in my code, except for the double form thing. No idea why it > would make a difference... and don't really think it should... but...... > > > > > > <snip> > > <html:form action="/authors-list"><html:submit > > property="submit"><bean:message > > key="authors-form.button.back"/></html:submit></html:form> > > <html:form action="/authors-list"><html:submit > > property="submit"><bean:message > > key="authors-form.button.forward"/></html:submit></html:form> > > </snip> > > > > And finally the Action-Map: > > <snip> > > protected Map getKeyMethodMap() { > > Map map = new HashMap(); > > map.put("authors-form.button.create", > > "create"); > > map.put("authors-form.button.edit", "edit"); > > map.put("authors-form.button.remove", > > "remove"); > > map.put("authors-form.button.forward", > > "forward"); > > map.put("authors-form.button.back", "back"); > > return map; > > } > > </snip> > > > > The back-button works, while the forward doesn't. > > > > The LookupDispatchAction tries to call a method named > > "weiter" instead > > of "forward", while it calls the "back"-method as expected. > > > > Alexander > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > 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]
