I’m having some issues with using an ajax refreshing component inside a loop, and I’m hoping someone can help. I have a component that contains an zone that I’m updating using a ajax request and an action link. In the onAction handler for the event link I do a data lookup based on an ID that I pass into the component as a paramter. Now if I have a page that contains this component and has a property that contains the data Id everything works fine. However if instead of a single data id I make the containing page have a property that is a List of data ids, loop over these ids in the template, for each one adding the component and passing the “current” id as a parameter I run into trouble. During the component’s “SetupRender” the parameter value is what I expect. However in the subsequent calls to the action link handler I discover that the parameter has reverted to “0”. It looks like at the point of the action link invocation, tapestry is trying to recompute the parameter value based on the containing page, but since the containing page doesn’t re-render, there is no loop and as a result the “current” loop iteration property is “0”. Can anyone suggest a way to get around this limitation?
Regards, Mike T
