This is due to the "same contents, but different physical value" problem
that has been described on this list.
An upgrade of For that resolves that issue has been checked in and
should be a part of the next beta. I believe it would address your
observations.
For the time being if you do need to use the previous betas, I would
suggest to use the 'keyExpression' parameter of For -- that is an OGNL
expression that extracts the primary key from the each object. For example:
keyExpression="userName"
Using keyExpression would force even the previous versions of For to use
the same values as those already provided.
Nick Stuart wrote:
Hi all, using beta 5 I've come across a problem with the new For loop
component. Using the old Foreach component I have a field in a form
tied to object properties that get looped over, nothing fancy. Using
this, doing the updates all the values for the individual objects are
update and saved.
However, using the new For loop, either, none of the values are
getting set, or none of the values/objects are being saved. The source
list for the loop is persistent and does stick around between requests
so thats ok. Not sure where else to check to fix this.
Anyone run into this before? If not I'll post some code to so a more
exact setup of the problem.
-Nick
---------------------------------------------------------------------
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]
