It seems like zone updates on form elements are quite difficult to perfect in tapestry. I simply want to update a select via a zone update and I'm finding myself attempting to work around the framework to get this to happen. I have a counter variable in my loop that is used when rendering all of my form elements. When a change to one of the selects triggers an update of a zone containing another select, the form relies on my now null counter variable to render it. Persisting the counter variable doesn't solve the problem, as that will always point to the last element encountered when iterating over my source objects in the loop. So, I'm left to figure out a way to track the state of all of my form elements on the server side via ajax (onValueChanged) calls. This sort of defeats the purpose of the loop element. I'm still hoping I do not understand how this works correctly.
On Mon, Jul 11, 2011 at 2:19 PM, Thiago H. de Paula Figueiredo < thiag...@gmail.com> wrote: > On Mon, 11 Jul 2011 15:54:02 -0300, Ray Nicholus <rnicho...@widen.com> > wrote: > > Note: I just noticed that the select component page for the select element >> includes an example that illustrates updating a select inside of a form via >> a zone update. I'm essentially trying to do the same thing, only with >> dynamically generated selects. >> > > Tapestry pages and components have strictly static structure. When inside a > Loop, a component can be rendered many times, but it's still a single > instance. > > > -- > Thiago H. de Paula Figueiredo > Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, > and instructor > Owner, Ars Machina Tecnologia da Informação Ltda. > http://www.arsmachina.com.br >
