I think you could do it a couple different ways...

1. 
JSP:
<bean:define id="lookupName" value="whateverLookupYouWantToGoto"/>
<html:link forward="test" paramId="updateMethod" paramName="lookupName"> 
...
</html:link>

2. 
JSP:
<html:link forward="gtest" >...</html:link>

struts config:
  <global-forwards>
          <forward   name="gtest"
          path="/test.do?updateMethod=whateverLookupYouWantToGoTo"/>
  </global-forwards>


I've done similar so either way should work.



-----Original Message-----
From: OFlaherty, Colm [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, August 06, 2003 11:35 AM
To: [EMAIL PROTECTED]
Subject: LookupDispatchAction error

I am getting the following error on , which I can't figure out:

HTTP ERROR: 500 Request[/test] does not contain handler parameter named
updateMethod
RequestURI=/clientdb/test.do


I am following a couple of decent examples using the LookupDispatchAction
class (pages 128 -130 in "Programming Jakarta Struts" by Chuck Cavaness). My
config is basically the same as what he has, but I have a couple of minor
differences, which I don't think should be causing any issues, but maybe
someone can put me right: 

The JSP link that gives me the error is the following: 

<tr><td><li><html:link forward="test"><bean:message
key="test.maintain.label"/></html:link></li></td></tr>

My action mappings section has the following action:


<action-mappings>
<action path="/test"
                type="com.kbcam.core.struts.action.TestUpdateAction" 
        name="testForm" 
        scope="request" 
        input="/pages/test.jsp" 
        parameter="updateMethod"
        >
</action>
...
</action-mappings>



I also have a section for the testForm: 


<form-beans>
<form-bean      name="testForm"
                        type="com.kbcam.core.struts.form.TestForm"/>
        ...
</form-beans>


My /pages/test.jsp uses a template, which points at /pages/testcontent.jsp,
which contains the following: 


<html:submit property="updateMethod">
<bean:message key="insert.label"/>
</html:submit>


As u would expect, the "insert.label" key is contained in the properties
file (as well as the "test.maintain.label"  from the initial link)


insert.label=Insert
test.maintain.label=Maintain Tests



My TestUpdateAction class has the following hierarchy and methods



LookupDispatchAction
              |
BaseLookupDispatchAction
              |
BaseUpdateAction (methods: getKeyMethodMap (),getKeyMethodMap (params),
insert (params), update (params), delete ()
                              (Maps "insert.label" to "insert")
              |
TestUpdateAction


My TestForm was generated using Xdoclet from the Test.java source code, and
has a protected "updateMethod" string variable, with a getter and setter.
TestForm is inherited from ActionForm


The kind of thing that I'm thinking might be causing the issue include: 

1.      The hierarchy of TestUpdateAction
2.      The fact that /pages/testcontent.jsp is not referenced directly, but
via the following lines in /pages/test.jsp: 
<template:insert template='/pages/template.jsp'>
<template:put name='content' content='/pages/testcontent.jsp'/> ...
3.      The calling link does NOT in a Form.  Its entire contents looks like
this: 

<%@ include file="/tags/taglibs.jsp" %>
<center>
<hr>
<table border="0" cellspacing="0" cellpadding="0">
        <tr><td><li><html:link forward="test"><bean:message
key="test.maintain.label"/></html:link></li></td></tr>
        <tr><td><li><html:link forward="logout"><bean:message
key="logout.label"/></html:link></li></td></tr>
</table>
</center>


Can anyone see anything I'm missing, or anything that I'm just doing
incorrectly?????  Any help is much appreciated.

Colm


**********************************************************************
This message is sent in confidence for the addressee
only.  The contents are not allowed to be disclosed to
anyone other than the addressee.  Unauthorised 
recipients must preserve this confidentiality and should 
please advise the sender immediately of any error in
transmission.
**********************************************************************


---------------------------------------------------------------------
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]

Reply via email to