As there are no dynamic component instances in Tapestry, there are no dynamic component-ids. What you are seeing (loopContacts_i, i=1 ...) are multiple clientId's (Element id's on the client side) rendere by one and the same component instance, whose id, the component-id on the server, is "loopContacts". So, tapestry wouldn't recognise loopContact_0 as a valid component-id anyway.
So, I'd just try to refresh "loopContacts" and see whether the overhead of refreshing all instances really hurts. > -----Original Message----- > From: Malin Ljungh [mailto:[EMAIL PROTECTED] > Sent: Friday, July 06, 2007 9:03 AM > To: Tapestry users > Subject: T4: Can I have dynamic component id or how do I solve this? > > I have a loop - a component of type="For", displaying contacts. > I'd like to have a component inside the loop with component > id equals something with the database key in it, the contact > ID. Is that possible? > > Or is there a smarter way to solve my issue? > The reason I want it this way is that I want to use it in > updateComponents with async="true". Then I could set > updateComponents to the desired contact ID that I want to > update on the client. > > All I have now is loopContacts, loopContacts_0, > loopContacts_1 and so on, but I don't know which contact is which... > > Hope someone understood something... :) > Any input appreciated!!! > > Malin > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
