The reason being is that most of the time storing an entire object
(serializing / size / etc ) is a huge amount of overhead both in terms of
bandwidth and server execution time.
You'd be better off using the "convert" / "keyExpression" or "primaryKeys"
parameter to the component - in which case only the very minimal needed to
match a specific object is stored in the form.
http://tapestry.apache.org/tapestry4.1/components/general/for.html
On 5/21/07, talk.small <[EMAIL PROTECTED]> wrote:
<form jwcid="cartForm">
<table class="shoppingcart">
<tr>
<td></td>
<td></td>
</tr>
</table>
</form>
I thought upon a rewind, the source="ognl:itemList" will not be evaluated
by
pulling data from server side database, becuase the itemlist has been
stores
as hidden fields in the generated html form. It is the items in hidden
fields that will be restored to the list for rewinding the loop.
But when I debug the page, the result is quite on the contrary:
getItemList() is got called in a rewinding to restore the data from
database. So why bother to store the list of items to as the hidden
fields,
since they seems no use for the submision?
BTW, I am using T4.0.2
--
View this message in context:
http://www.nabble.com/Does-the-%27source%27-of-%40For-in-a-form-got-evaluated-during-a-rewind---tf3793753.html#a10730070
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
