I am using tomcat 5 which I believe has jsp 2.0
I am getting exception of users getters/setters not defined exception.
it assumes users as one of the attribute of my form instead of Collection.
Digant
"Michael Jouravlev" <[EMAIL PROTECTED]>
02/21/2006 01:08 PM
Please respond to "Struts Users Mailing List"
To: "Struts Users Mailing List" <user@struts.apache.org>
cc:
Subject: Re: drop down list box question.
On 2/21/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]>
wrote:
> I have users list created in my dispatch action and populated in
request.
>
>
> in my form this works.
> ........
> <tr>
> <td class="tdLabel"><fmt:message key="label.endDate"/>:</td>
> <td><html:text property="endDate" size="40"/> <html:errors
> property="endDate"/></td>
> </tr>
> <tr>
> <td class="tdLabel"><fmt:message
> key="label.oddLotOwnerUserName"/>:</td>
> <td>
> <html:select property="oddLotOwnerUserId">
> <c:forEach var="user" items="${users}">
> <html:option value="${user.userId}">
> <c:out value="${user.userNameShort}"/>
> </html:option>
> </c:forEach>
> </html:select>
> </td>
> </tr>
> .......
>
> But This DOESN'T work.
> <tr>
> <td class="tdLabel"><fmt:message key="label.endDate"/>:</td>
> <td><html:text property="endDate" size="40"/> <html:errors
> property="endDate"/></td>
> </tr>
>
> <tr>
> <td class="tdLabel"><fmt:message
> key="label.oddLotOwnerUserName"/>:</td>
> <html:select property="oddLotOwnerUserId" >
> <html:optionsCollection property="users"
> value="${user.userId}"
> label="${user.userNameShort}" />
> </html:select>
> </tr>
> What am I doing wrong ??
What exactly does not work? Do you use JSP 2.x container?
Michael.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This communication is for informational purposes only. It is not intended
as an offer or solicitation for the purchase or sale of any financial
instrument or as an official confirmation of any transaction. All market prices,
data and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries
and affiliates
