Pai is correct. UpdateComponent() must be passed a component ID. An
arbitrary ID does not work.
--
Kevin
On 1/16/08 12:40 PM, in article [EMAIL PROTECTED], "Pai911"
<[EMAIL PROTECTED]> wrote:
>
> Hi!
> Maybe you should make the division you want to update Tapestry components?
>
> <div id="[EMAIL PROTECTED]">
> <div jwcid="@RenderBlock" block="ognl:components.autoPagingContent" />
> </div>
> <div id="[EMAIL PROTECTED]">
> <div jwcid="@RenderBlock" block="ognl:components.collectionContent" />
> </div>
> <div id="[EMAIL PROTECTED]">
> <div jwcid="@RenderBlock" block="ognl:components.autoPagingContent" />
> </div>
>
>
> nhhockeyplayer wrote:
>>
>>
>> Well I tried this in the page that contains the component...
>>
>> public void refresh()
>> {
>> getResponseBuilder().updateComponent("headerSelect");
>> getResponseBuilder().updateComponent("footerSelect");
>> }
>>
>> Since these are my dom references...
>> <div id="headerSelect">
>> <div jwcid="@RenderBlock" block="ognl:components.autoPagingContent" />
>> </div>
>> <div id="galleryContent">
>> <div jwcid="@RenderBlock" block="ognl:components.collectionContent" />
>> </div>
>> <div id="footerSelect">
>> <div jwcid="@RenderBlock" block="ognl:components.autoPagingContent" />
>> </div>
>>
>> and this does not cut it.
>>
>> I am looking at cometd sample in tacos and it looks like I need to
>> establish a scripting interface?
>>
>> Can anyone confirm? Is there an easier quicker way to update a dom
>> referring to a widget from the server side?
>> Thanks in advance...
>> Best regards Ken in nashua
>>
>>
>> From: [EMAIL PROTECTED]: [EMAIL PROTECTED]:
>> bidirectional dom interfaceDate: Wed, 16 Jan 2008 08:15:02 -0500
>>
>>
>> Hi Folks, I am impressed with this interface.
>> @EventListener(events = { "onchange" }, targets = { "pagingSpanSelect" },
>> submitForm = "myForm", async = true)
>>
>> public void pagingSpanListener(IRequestCycle cycle)
>>
>> {} It provides a nice interface from DOM into server side. But How do I
>> talk to my dom javascript node from here? Is there a way to reference the
>> form and set a value of a dom node that models a tapestry widget ? Why do
>> I need this? Well My tapestry widget is modeled to a dom node A. But I
>> actually used the @Block declaration to model another dom B node to the
>> same widget... When I change A, B stays the same. I need to update the
>> other dom node when one changes. Thanks for any tips.Best regards Ken in
>> nashua
>>
>> Get the power of Windows + Web with the new Windows Live. Get it now!
>> _________________________________________________________________
>> Make distant family not so distant with Windows Vista® + Windows Live.
>> http://www.microsoft.com/windows/digitallife/keepintouch.mspx?ocid=TXT_TAGLM_
>> CPC_VideoChat_distantfamily_012008
>>
>> -----
>> Best regards
>> Ken in nashua
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
