Hi Dave,
here is complete jsp:
<s:iterator value="activeOrder.orderList" status="rowstatus">
<tr id="row_<s:property value="reference"/>" class="odd">
<td>
<s:text name="order.ref" >
<s:param name="value" value="reference"/> <- THIS WORKS
</s:text>
</td>
<s:if test="#session.order != null"> <- order in session is
recognized
<td>
<s:text name="order.price" >
<s:param name="value"
value="#session.order.orderList[#rowstatus.index].price"/> <- null values
</s:text>
</td>
</s:if>
<td>
<s:text name="order.price" >
<s:param name="value" value="price"/> <- HERE IT WORKS, from
activeOrder.
</s:text>
</td>
</tr>
</s:iterator>
I checked many times if I have orderList in my session and I have orderList
in it filled.
--
Milan
newton.dave wrote:
>
> --- On Mon, 8/25/08, Milan Milanovic wrote:
>> <s:if test="#session.order != null">
>> <- HERE IT WORKS (order is recognized
>> in session)!!
>> <td>
>> <s:text name="order.price" >
>> <s:param name="value"
>> value="#session.order.orderList[#rowstatus.index].price"/>
>> <- HERE IT
>> DOESN'T WORK - null value!
>> </s:text>
>> </td>
>> </s:if>
>
> "IT" is two *entirely different expressions*, and you continue to provide
> no additional information that might be usable to solve the problem. It's
> not an OGNL syntax issue. If you want more help, provide more details.
>
> (IIRC I also didn't use <s:param...>'s "name" attribute; I don't think
> it's necessary, although I don't know if the presence of it will cause the
> message to be parameterized incorrectly.)
>
> Dave
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/-S2--Iterate-through-two-lists-tp19052842p19147809.html
Sent from the Struts - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
