This was the issue with refresh.
https://issues.apache.org/jira/browse/TAPESTRY-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561377#action_12561377Best
regards Ken in nashua
From: [EMAIL PROTECTED]: [EMAIL PROTECTED]: bidirectional dom interfac
this part of my code
thanks for your time
nirvdrum wrote:
>
> Is customerTable a Tapestry component or is it an ID you just attached to
> some element?
>
> --
> Kevin
>
>
> On 1/17/08 10:12 AM, in article [EMAIL PROTECT
Is customerTable a Tapestry component or is it an ID you just attached to
some element?
--
Kevin
On 1/17/08 10:12 AM, in article [EMAIL PROTECTED],
"DR_GLoPeL_BouCa" <[EMAIL PROTECTED]> wrote:
>
> Hello people, I've the similar problem, the browser not display the response
> of ajax submit, I
Thiago H de Paula Figueiredo-2 wrote:
>
> On Jan 17, 2008 12:12 PM, DR_GLoPeL_BouCa <[EMAIL PROTECTED]> wrote:
>
>>
>> Hello people, I've the similar problem, the browser not display the
>> response
>> of ajax submit, I've form with submit async="true" and
>> updateComponents="ognl:customerTab
On Jan 17, 2008 12:12 PM, DR_GLoPeL_BouCa <[EMAIL PROTECTED]> wrote:
>
> Hello people, I've the similar problem, the browser not display the
> response
> of ajax submit, I've form with submit async="true" and
> updateComponents="ognl:customerTable", when the ajax response come browser
> don't disp
Hello people, I've the similar problem, the browser not display the response
of ajax submit, I've form with submit async="true" and
updateComponents="ognl:customerTable", when the ajax response come browser
don't display any change, but in the fireBug bar, inspect de response and is
in there, what
Hi!
What if you try
/*Put the content you want to be displayed right here*/
/*Don't use render block */
nhhockeyplayer wrote:
>
>
> Well the fact that one definition refers to the same ognl instance being
> "ognl:components.autoPagingContent" commonsense tells me I shouldn't even
> sho
Well the fact that one definition refers to the same ognl instance being
"ognl:components.autoPagingContent" commonsense tells me I shouldn't even
should be mucking with this... it should update automatically.
The fact that this component's PropertySelect doesn't even survive a page
I could be mistaken, but I think if you have the component in a loop, then
updateComponent("baseIdName") will apply to all of those components in the
loop . . . I.e., you don't have to specify each individual instance.
If you're running into issues with grouping though, you could surround the
the
more feedback...
I tried this explicitly
getResponseBuilder().updateComponent("tableSizeSelect_0");
and it did not update the select dom with the expected value that lives in the
other select dom
getResponseBuilder().updateComponent("tableSizeSelect");
Best regards Ken in nashua
From: [E
Ok, I fixed the ID issue...
But... it don't work.
What don't Work? more than one DOM referencing one instance of a tapestry
component/widget... namely a PropertySelect.
Here is the proof. I did view-source fro the browser to look at the markup.
markup...
...
Now will HTML crap out if
Well it's probably because the ID has changed now to
id="[EMAIL PROTECTED]"
OK, so I should use jwcid.Best regards Ken in nashua
From: [EMAIL PROTECTED]: [EMAIL PROTECTED]: RE: bidirectional dom
interfaceDate: Wed, 16 Jan 2008 10:44:32 -0500
Well I tried this in the page that contains t
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?
>
>
>
>
PAI,
I tried your suggestion on the ANY component.
My Gallery.script is being impacted now.
I cannot do the following:
// just paste a Loading text at bottom of table
// this worked previously to your suggestion
var divBlock = document.createElement("div");
divBlock.appendChild(document.
Hi!
Maybe you should make the division you want to update Tapestry components?
nhhockeyplayer wrote:
>
>
> Well I tried this in the page that contains the component...
>
> public void refresh()
> {
> getResponseBuilder().updateComponent("headerSelect");
> getResponseBuil
getResponseBuilder().updateComponent is the way to update parts of your
view.
Check if your html is correct.
On Jan 16, 2008 4:44 PM, Ken in nashua <[EMAIL PROTECTED]> wrote:
>
> Well I tried this in the page that contains the component...
>
> public void refresh()
> {
> getResponseBuilder().upda
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...
and this does not cut it.
I am looking at come
17 matches
Mail list logo
