Ray, I think the ValueEncoder is doing what you are looking for in George's example. When the loop is rendered the encoder helps figure out a unique id to encode into the form so that when you make a change an trigger the zone update, that id is handed back to the encoder and it sets purchaseRequest back to the value it was when the form originally rendered that iteration of the loop.
So to answer your question, no. The purchaseRequest isn't set to the last instance it encountered--it gets reset to whatever it was at that particular point in time. Does that help? Mark On Tue, Jul 12, 2011 at 2:24 PM, Ray Nicholus <rnicho...@widen.com> wrote: > When the select in your loopZone reloads after the zone update, it uses > purchaseRequest to determine it's value. However, after the loop has > already executed, purchaseRequest, which you persist, points to the last > purchaseRequest instant enountered by the ajaxformloop. Correct? > > On Tue, Jul 12, 2011 at 2:14 PM, George Christman > <gchrist...@cardaddy.com>wrote: > >> I might not be understanding your question completely, so please correct me >> if I'm misunderstanding you. The sample code I posted enables you to only >> update the zone within the row of the select menu triggering it. If you >> select an option in the first select menu / first row, it will only update >> the zone in the first row and not the last row. >> >> -- >> View this message in context: >> http://tapestry.1045711.n5.nabble.com/updating-a-zone-inside-of-an-ajaxformloop-tp4575519p4579967.html >> Sent from the Tapestry - User mailing list archive at Nabble.com. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >> For additional commands, e-mail: users-h...@tapestry.apache.org >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
