I have opened a bug about this issue (#1556190).
I see its still open so i guess you can close it.
Thanks,
Tomer
Eelco Hillenius wrote:
Ah, cool.
Eelco
On 9/13/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
actually i think its already been fixed
action type=fix dev=Matej Knopp
Could you add a bug report please?
Eelco
On 9/11/06, Nili Adoram [EMAIL PROTECTED] wrote:
After a long testing cycle we've discovered the problem.
Since we work in development mode, by default Page.checkRendering()
verifies that all page components were indeed rendered.
When each component
actually i think its already been fixed action type=fix dev=Matej Knopp due-to=Tomer MevorachAjaxRequestTarget now doesn't switch component use check off, as it is no longer needed./action
-IgorOn 9/13/06, Eelco Hillenius [EMAIL PROTECTED] wrote:
Could you add a bug report please?EelcoOn 9/11/06,
Ah, cool.
Eelco
On 9/13/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
actually i think its already been fixed
action type=fix dev=Matej Knopp due-to=Tomer
MevorachAjaxRequestTarget now doesn't switch component use check off, as
it is no longer needed./action
-Igor
On 9/13/06,
After a long testing cycle we've discovered the problem.
Since we work in development mode, by default Page.checkRendering()
verifies that all page components were indeed rendered.
When each component is rendered it calls Page.componentRendered().
This method is responsible for adding the calling
Could this be a race between Ajax and synchronized rendering?
Is it possible that Ajax has removed nodes from the DOM and the when
Page tries to render itself it does not find the components in the markup?
Tomer Mevorach wrote:
Hi,
My application works fine most of the time, however, sometimes
Hi,
My application works fine most of the time, however, sometimes an
exception indicating a mismatch between java and html component's
hierarchy is thrown.
I can't think of a test case that generates this exception as it is
thrown inconsistently.
can anyone please help figure out the problem.
