Re: Trouble updating component after async. directlink : clientId's generated in For-loops

2006-11-22 Thread Kim Thrysøe
Thank you for the response. That is exactly what I wanted. But ... something is still odd. I get too and mixed up updates back to in the ajax-response requests. Is this a bug or expected behaviour? _Click on first row :_ Tapestry / DojoAjaxResponseBuilder sends * (actually containing both fi

Trouble updating component after async. directlink : clientId's generated in For-loops

2006-11-21 Thread Kim Thrysøe
In a page containing elements generated by a component placed under a For-Loop component I want to be able to update a single such component/element using the very nifty "DojoAjaxResponseBuilder.updateComponent()" feature. In summary I want to have a DirectLink for each row in a table. The l

Re: Re: Trouble updating component after async. directlink : clientId's generated in For-loops

2006-11-21 Thread Sam Gendler
On 11/21/06, andyhot <[EMAIL PROTECTED]> wrote: updateComponents="ognl:components.therow.clientId" Can I suggest that we get this into the docs in some way. It stumps a lot of people, including myself. Also, it seems like if I want to update a component by calling ResponseBuilder.updateCompo

Re: Trouble updating component after async. directlink : clientId's generated in For-loops

2006-11-21 Thread andyhot
Sam Gendler wrote: > On 11/21/06, andyhot <[EMAIL PROTECTED]> wrote: >> updateComponents="ognl:components.therow.clientId" >> > > Can I suggest that we get this into the docs in some way. It stumps a > lot of people, including myself. http://issues.apache.org/jira/browse/TAPESTRY-1137 proposes a