Hi Chand,
        As far as I understand your question. Your application has an
entity called ITEM, which has 2 attributes one is CODE for the ITEM and
another is NAME for the ITEM. Now in the screen you wanted to display
one attribute (i.e. the CODE of the ITEM or the NAME of the ITEM) where
as after submission inside the ACTION class you want both the
information i.e. the CODE and the NAME of the ITEM.

        Here are the possible solutions.

1) As everyone in the mailing list who has replied prior to me you can
STORE the Data object which you created while displaying the ITEM
information in the JSP page in the session. And display only CODE of the
ITEM in the page. In the session, you store the information in form of a
MAP which accepts CODE of the ITEM as the Key and NAME of the ITEM as
the value. Now when the jsp page is submitted, you would anyways get the
selected ITEM's CODE. With the CODE value you can retrieve the NAME of
the ITEM in the Action class since you already have that information in
the session object.

2) Secondly if you don't want to store the data object in the session.
And you want the information in the form of hidden fields  One simple
and straight forward way is you can store all the ITEM's information
lets say the CODE and NAME as hidden attributes. 


<logic:iterate id="rows" name="APPROPRIATE BEAN NAME" property="PROPERTY
NAME" indexId="i">

  <input type="hidden" name="items[<bean:write name='i' />].name"
value="<bean:write name='ItemType' property='name' />" />

  <input type="hidden" name="items[<bean:write name='i' />].code"
value="<bean:write name='ItemType' property='code' />" />

</logic:iterate>


        After submission, you would anyway get the Selected ITEM's CODE
and you get the ITEM code and Item Name from by doing a
request.getParameter.

Or if you don't want to store all the codes as hidden attributes, here
is another way, instead of "Index I" try to store the name attribute
like

Items [YOUR CODE VALUE].name = YOUR NAME VALUE.

Have a Good Day!!!
Best Regards
Pal

-----Original Message-----
From: Tamas Szabo [mailto:[EMAIL PROTECTED] 
Sent: Saturday, November 26, 2005 1:31 AM
To: Struts Users Mailing List
Subject: Re: saving a value in jsp?

Hi,

I think somebody already explained you that you don't need the name.
In the Action to which you forward you can loop up the name based on the
code.

But if you stick to this then you can create a hidden field called name
and
on the onChange of the dropdown list set the value of the hidden field
to
the selected name.


Tamas


On 11/25/05, Kanuri, Chand <[EMAIL PROTECTED]> wrote:
>
> hi all,
> i have a dropdown list in my struts web app,
> i am having a form in which a bean is instatiated(bean has 2
properties
> "name" and "code").
>
> i am using like this in the jsp:
>
> <td><html:select property="item.code">
>
>                                         <logic:iterate id="itemType"
>
> name="<%=WebConstants.getItemTypeListName()%>">
>                                                 <option
value='<bean:write
> name="ItemType" property="code"/>'><bean:write
>
name="ItemType"
> property="name" /></option>
>                                         </logic:iterate>
>
>
>                                 </html:select></td>
>
> each "itemType" has "code" and "name".
> when the user clicks on the item name on the dropdown item beans
"code" is
> populating.now i need to populate "name" aswell at the sametime using
> hidden
> property.
>
> i want to save tha value of name in the jsp to use it later to
populate
> "name" in my form using hidden property?
>
> do anyone have idea how to save the value in jsp?
>
> regards and thanks in advance
>
>
> This e-mail (and any attachments) may contain privileged and/or
> confidential information. If you are not the intended recipient please
do
> not disclose, copy, distribute, disseminate or take any action in
reliance
> on it. If you have received this message in error please reply and
tell us
> and then delete it. Should you wish to communicate with us by e-mail
we
> cannot guarantee the security of any data outside our own computer
systems.
> For the protection of Legal & General's systems and staff, incoming
emails
> will be automatically scanned.
>
> Any information contained in this message may be subject to applicable
> terms and conditions and must not be construed as giving investment
advice
> within or outside the United Kingdom.
>
> The following companies are subsidiary companies of the Legal &
General
> Group Plc which are authorised and regulated by the Financial Services
> Authority for advising and arranging the products shown: Legal &
General
> Partnership Services Limited (insurance and mortgages), Legal &
General
> Insurance Limited (insurance), Legal & General Assurance Society
Limited
> (life assurance, pensions and investments), Legal & General Unit Trust
> Managers Limited and Legal & General Portfolio Management Services
Limited
> (investments).
>
> They are registered in England under numbers shown.
> The registered office is Temple Court, 11 Queen Victoria Street,
London
> EC4N 4TP.
>
> Legal & General Partnership Services Limited: 5045000 Legal & General
> Assurance Society Limited: 166055 Legal & General (Unit Trust
Managers)
> Limited: 1009418 Legal & General (Portfolio Management Services)
Limited:
> 2457525 Legal & General Insurance Limited: 423930
>
> They are registered with the Financial Services Authority under
numbers
> shown. You can check this at www.fsa.gov.uk/register
>
> Legal & General Partnership Services Limited: 300792 Legal & General
> Assurance Society Limited: 117659 Legal & General (Unit Trust
Managers)
> Limited: 119273 Legal & General (Portfolio Management Services)
Limited:
> 146786 Legal & General Insurance Limited: 202050
>
>
> ---------------------------------------------------------------------
> 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