Hi,
It won't help to find a cause, but I can confirm that I observe
exactly the same behaviour in my application.
Regards
Lukasz
W dniu 3 czerwca 2009 00:35 użytkownik grabarz napisał:
> hi,
> thanks for that solution!
>
> i will try to find a reason of this strange behaviour debugging
> tapest
hi,
thanks for that solution!
i will try to find a reason of this strange behaviour debugging
tapestry's sources. in worst case i will give up using your workaround.
best regards,
m.
Moritz Gmelin wrote on 02 Jun 2009 20:52:58 MET:
> Hi,
>
> I had a very similar problem today too. Sometimes th
isn't it related to some kind of caching? the strange thing is that it
is fairly enough to refresh the page to get everything running
again... for a few minutes. after next few ajaxized updates
component's body is being ignored again.
i'm about to debug tapestry's core. is there any point that co
I can't think of anything that could explain what you are seeing. Full
and partial page rendering operate on the page structure identically.
2009/6/2 grabarz :
> hi,
> this is one of these 'mysterious' problems. i have a component (report)
> which takes a datasource and draws a table filled with d
Hi,
I had a very similar problem today too. Sometimes the body was
rendered, other times just nothing was rendered.
My workaround was to define a block containing the body part, pass
this block to the "report" and have it rendered through to="passedBlock" />
your report.tml would look lik
hi,
this is one of these 'mysterious' problems. i have a component (report)
which takes a datasource and draws a table filled with data. something
like a grid component provided by tapestry.
this is essencial part of .tml:
test
