You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Xavier Hanin (JIRA)" <ji...@apache.org> on 2007/05/23 10:44:16 UTC
[jira] Created: (WICKET-589) problem with Ajax and rendering
problem with Ajax and rendering
-------------------------------
Key: WICKET-589
URL: https://issues.apache.org/jira/browse/WICKET-589
Project: Wicket
Issue Type: Bug
Components: wicket
Affects Versions: 1.3.0-beta2
Environment: wicket build from svn trunk revision 540588
Reporter: Xavier Hanin
Problem description copied from the mailing list:
After upgrading from wicket 1.3 beta 1 to a build based on revision 540588, I get the following error message:
18:49:19.245 [btpool0-2] ERROR org.apache.wicket.RequestCycle - The
component(s) below failed to render. A common problem is that you have
added a component in code but forgot to reference it in the markup
(thus the component will never be rendered).
1. [MarkupContainer [Component id = progressBarStylesheet, page =
org.xoocode.xooctory.web.pages.dashboard.Dashboard, path =
2:projects-panel:projects:6:leftTimePanel:progressBar:progressBarStylesheet.StyleSheetReference,
isVisible = true, isVersioned = false]]
The problem is that the component is properly added, and it worked
before upgrading, so...
So I've tried to track down the problem, and I've not found the source
of the problem. As a workaround I disable check rendering with:
getDebugSettings().setComponentUseCheck(false);
Then everything works properly, and the component (a style sheet) is
properly rendered.
Let me explain a little bit more the situation in which the problem occurs.
The component which is causing the problem is a StyleSheetReference
added to a panel. The markup contains the corresponding link in a
wicket:head section.
The panel is invisible when the page is loaded, but then I use an ajax
link to trigger an action, which later triggers the visibility of this
component to true. Then this component is refreshed by an AjaxTimer
(actually I use wicket-contrib-push, but I don't think it really makes
a difference, since it's using a simple AbstractAjaxTimerBehavior
underneath). And that's when the component is rendered that the check
rendering is failing. Some analysis shown that there's a
StyleSheetReference with the good id in the renderedComponent
attribute of Page, but it isn't the exact same StyleSheetReference
instance as the one checked by the checkRendering method. For the
moment I haven't managed to really see why I have two instances, what
doesn't help is that it seems that when I debug, the problem goes away
depending on the occurence of other timer based ajax requests.
For more details the sources are available here:
ProgressBar.java
http://www.xoocode.org/wsvn/xoocode/org.xoocode.xooctory/trunk/xooctory/src/main/java/org/xoocode/xooctory/web/component/ProgressBar.java?op=file&rev=189&sc=0
ProgressBar.html
http://www.xoocode.org/wsvn/xoocode/org.xoocode.xooctory/trunk/xooctory/src/main/java/org/xoocode/xooctory/web/component/ProgressBar.html?op=file&rev=166&sc=0
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-589) problem with Ajax and rendering
Posted by "Alastair Maw (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alastair Maw updated WICKET-589:
--------------------------------
Fix Version/s: 1.3.0-rc1
Affects Version/s: (was: 1.3.0-beta2)
Is this still an issue? Please create a quickstart project if so and we'll debug it.
> problem with Ajax and rendering
> -------------------------------
>
> Key: WICKET-589
> URL: https://issues.apache.org/jira/browse/WICKET-589
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Environment: wicket build from svn trunk revision 540588
> Reporter: Xavier Hanin
> Fix For: 1.3.0-rc1
>
>
> Problem description copied from the mailing list:
> After upgrading from wicket 1.3 beta 1 to a build based on revision 540588, I get the following error message:
> 18:49:19.245 [btpool0-2] ERROR org.apache.wicket.RequestCycle - The
> component(s) below failed to render. A common problem is that you have
> added a component in code but forgot to reference it in the markup
> (thus the component will never be rendered).
> 1. [MarkupContainer [Component id = progressBarStylesheet, page =
> org.xoocode.xooctory.web.pages.dashboard.Dashboard, path =
> 2:projects-panel:projects:6:leftTimePanel:progressBar:progressBarStylesheet.StyleSheetReference,
> isVisible = true, isVersioned = false]]
> The problem is that the component is properly added, and it worked
> before upgrading, so...
> So I've tried to track down the problem, and I've not found the source
> of the problem. As a workaround I disable check rendering with:
> getDebugSettings().setComponentUseCheck(false);
> Then everything works properly, and the component (a style sheet) is
> properly rendered.
> Let me explain a little bit more the situation in which the problem occurs.
> The component which is causing the problem is a StyleSheetReference
> added to a panel. The markup contains the corresponding link in a
> wicket:head section.
> The panel is invisible when the page is loaded, but then I use an ajax
> link to trigger an action, which later triggers the visibility of this
> component to true. Then this component is refreshed by an AjaxTimer
> (actually I use wicket-contrib-push, but I don't think it really makes
> a difference, since it's using a simple AbstractAjaxTimerBehavior
> underneath). And that's when the component is rendered that the check
> rendering is failing. Some analysis shown that there's a
> StyleSheetReference with the good id in the renderedComponent
> attribute of Page, but it isn't the exact same StyleSheetReference
> instance as the one checked by the checkRendering method. For the
> moment I haven't managed to really see why I have two instances, what
> doesn't help is that it seems that when I debug, the problem goes away
> depending on the occurence of other timer based ajax requests.
> For more details the sources are available here:
> ProgressBar.java
> http://www.xoocode.org/wsvn/xoocode/org.xoocode.xooctory/trunk/xooctory/src/main/java/org/xoocode/xooctory/web/component/ProgressBar.java?op=file&rev=189&sc=0
> ProgressBar.html
> http://www.xoocode.org/wsvn/xoocode/org.xoocode.xooctory/trunk/xooctory/src/main/java/org/xoocode/xooctory/web/component/ProgressBar.html?op=file&rev=166&sc=0
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-589) problem with Ajax and rendering
Posted by "Xavier Hanin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503300 ]
Xavier Hanin commented on WICKET-589:
-------------------------------------
I don't know if it's still an issue or not, I haven't upgraded wicket since then. I will try with a new fresh build from current latest revision and tell you if I still have the problem.
> problem with Ajax and rendering
> -------------------------------
>
> Key: WICKET-589
> URL: https://issues.apache.org/jira/browse/WICKET-589
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Environment: wicket build from svn trunk revision 540588
> Reporter: Xavier Hanin
> Assignee: Matej Knopp
> Fix For: 1.3.0-rc1
>
>
> Problem description copied from the mailing list:
> After upgrading from wicket 1.3 beta 1 to a build based on revision 540588, I get the following error message:
> 18:49:19.245 [btpool0-2] ERROR org.apache.wicket.RequestCycle - The
> component(s) below failed to render. A common problem is that you have
> added a component in code but forgot to reference it in the markup
> (thus the component will never be rendered).
> 1. [MarkupContainer [Component id = progressBarStylesheet, page =
> org.xoocode.xooctory.web.pages.dashboard.Dashboard, path =
> 2:projects-panel:projects:6:leftTimePanel:progressBar:progressBarStylesheet.StyleSheetReference,
> isVisible = true, isVersioned = false]]
> The problem is that the component is properly added, and it worked
> before upgrading, so...
> So I've tried to track down the problem, and I've not found the source
> of the problem. As a workaround I disable check rendering with:
> getDebugSettings().setComponentUseCheck(false);
> Then everything works properly, and the component (a style sheet) is
> properly rendered.
> Let me explain a little bit more the situation in which the problem occurs.
> The component which is causing the problem is a StyleSheetReference
> added to a panel. The markup contains the corresponding link in a
> wicket:head section.
> The panel is invisible when the page is loaded, but then I use an ajax
> link to trigger an action, which later triggers the visibility of this
> component to true. Then this component is refreshed by an AjaxTimer
> (actually I use wicket-contrib-push, but I don't think it really makes
> a difference, since it's using a simple AbstractAjaxTimerBehavior
> underneath). And that's when the component is rendered that the check
> rendering is failing. Some analysis shown that there's a
> StyleSheetReference with the good id in the renderedComponent
> attribute of Page, but it isn't the exact same StyleSheetReference
> instance as the one checked by the checkRendering method. For the
> moment I haven't managed to really see why I have two instances, what
> doesn't help is that it seems that when I debug, the problem goes away
> depending on the occurence of other timer based ajax requests.
> For more details the sources are available here:
> ProgressBar.java
> http://www.xoocode.org/wsvn/xoocode/org.xoocode.xooctory/trunk/xooctory/src/main/java/org/xoocode/xooctory/web/component/ProgressBar.java?op=file&rev=189&sc=0
> ProgressBar.html
> http://www.xoocode.org/wsvn/xoocode/org.xoocode.xooctory/trunk/xooctory/src/main/java/org/xoocode/xooctory/web/component/ProgressBar.html?op=file&rev=166&sc=0
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-589) problem with Ajax and rendering
Posted by "Matej Knopp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503376 ]
Matej Knopp commented on WICKET-589:
------------------------------------
I tried to reproduce it but i couldn't. Can you please confirm if it is still relevant and if it is provide a quickstart?
> problem with Ajax and rendering
> -------------------------------
>
> Key: WICKET-589
> URL: https://issues.apache.org/jira/browse/WICKET-589
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Environment: wicket build from svn trunk revision 540588
> Reporter: Xavier Hanin
> Assignee: Matej Knopp
> Fix For: 1.3.0-rc1
>
>
> Problem description copied from the mailing list:
> After upgrading from wicket 1.3 beta 1 to a build based on revision 540588, I get the following error message:
> 18:49:19.245 [btpool0-2] ERROR org.apache.wicket.RequestCycle - The
> component(s) below failed to render. A common problem is that you have
> added a component in code but forgot to reference it in the markup
> (thus the component will never be rendered).
> 1. [MarkupContainer [Component id = progressBarStylesheet, page =
> org.xoocode.xooctory.web.pages.dashboard.Dashboard, path =
> 2:projects-panel:projects:6:leftTimePanel:progressBar:progressBarStylesheet.StyleSheetReference,
> isVisible = true, isVersioned = false]]
> The problem is that the component is properly added, and it worked
> before upgrading, so...
> So I've tried to track down the problem, and I've not found the source
> of the problem. As a workaround I disable check rendering with:
> getDebugSettings().setComponentUseCheck(false);
> Then everything works properly, and the component (a style sheet) is
> properly rendered.
> Let me explain a little bit more the situation in which the problem occurs.
> The component which is causing the problem is a StyleSheetReference
> added to a panel. The markup contains the corresponding link in a
> wicket:head section.
> The panel is invisible when the page is loaded, but then I use an ajax
> link to trigger an action, which later triggers the visibility of this
> component to true. Then this component is refreshed by an AjaxTimer
> (actually I use wicket-contrib-push, but I don't think it really makes
> a difference, since it's using a simple AbstractAjaxTimerBehavior
> underneath). And that's when the component is rendered that the check
> rendering is failing. Some analysis shown that there's a
> StyleSheetReference with the good id in the renderedComponent
> attribute of Page, but it isn't the exact same StyleSheetReference
> instance as the one checked by the checkRendering method. For the
> moment I haven't managed to really see why I have two instances, what
> doesn't help is that it seems that when I debug, the problem goes away
> depending on the occurence of other timer based ajax requests.
> For more details the sources are available here:
> ProgressBar.java
> http://www.xoocode.org/wsvn/xoocode/org.xoocode.xooctory/trunk/xooctory/src/main/java/org/xoocode/xooctory/web/component/ProgressBar.java?op=file&rev=189&sc=0
> ProgressBar.html
> http://www.xoocode.org/wsvn/xoocode/org.xoocode.xooctory/trunk/xooctory/src/main/java/org/xoocode/xooctory/web/component/ProgressBar.html?op=file&rev=166&sc=0
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (WICKET-589) problem with Ajax and rendering
Posted by "Alastair Maw (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alastair Maw resolved WICKET-589.
---------------------------------
Resolution: Cannot Reproduce
Fix Version/s: (was: 1.3.0-rc1)
1.3.0-beta2
I'm considering it an artefact of trunk development, rather than something that should make the changelog, anyway, so this is getting marked cannot reproduce.
> problem with Ajax and rendering
> -------------------------------
>
> Key: WICKET-589
> URL: https://issues.apache.org/jira/browse/WICKET-589
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Environment: wicket build from svn trunk revision 540588
> Reporter: Xavier Hanin
> Assignee: Matej Knopp
> Fix For: 1.3.0-beta2
>
>
> Problem description copied from the mailing list:
> After upgrading from wicket 1.3 beta 1 to a build based on revision 540588, I get the following error message:
> 18:49:19.245 [btpool0-2] ERROR org.apache.wicket.RequestCycle - The
> component(s) below failed to render. A common problem is that you have
> added a component in code but forgot to reference it in the markup
> (thus the component will never be rendered).
> 1. [MarkupContainer [Component id = progressBarStylesheet, page =
> org.xoocode.xooctory.web.pages.dashboard.Dashboard, path =
> 2:projects-panel:projects:6:leftTimePanel:progressBar:progressBarStylesheet.StyleSheetReference,
> isVisible = true, isVersioned = false]]
> The problem is that the component is properly added, and it worked
> before upgrading, so...
> So I've tried to track down the problem, and I've not found the source
> of the problem. As a workaround I disable check rendering with:
> getDebugSettings().setComponentUseCheck(false);
> Then everything works properly, and the component (a style sheet) is
> properly rendered.
> Let me explain a little bit more the situation in which the problem occurs.
> The component which is causing the problem is a StyleSheetReference
> added to a panel. The markup contains the corresponding link in a
> wicket:head section.
> The panel is invisible when the page is loaded, but then I use an ajax
> link to trigger an action, which later triggers the visibility of this
> component to true. Then this component is refreshed by an AjaxTimer
> (actually I use wicket-contrib-push, but I don't think it really makes
> a difference, since it's using a simple AbstractAjaxTimerBehavior
> underneath). And that's when the component is rendered that the check
> rendering is failing. Some analysis shown that there's a
> StyleSheetReference with the good id in the renderedComponent
> attribute of Page, but it isn't the exact same StyleSheetReference
> instance as the one checked by the checkRendering method. For the
> moment I haven't managed to really see why I have two instances, what
> doesn't help is that it seems that when I debug, the problem goes away
> depending on the occurence of other timer based ajax requests.
> For more details the sources are available here:
> ProgressBar.java
> http://www.xoocode.org/wsvn/xoocode/org.xoocode.xooctory/trunk/xooctory/src/main/java/org/xoocode/xooctory/web/component/ProgressBar.java?op=file&rev=189&sc=0
> ProgressBar.html
> http://www.xoocode.org/wsvn/xoocode/org.xoocode.xooctory/trunk/xooctory/src/main/java/org/xoocode/xooctory/web/component/ProgressBar.html?op=file&rev=166&sc=0
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-589) problem with Ajax and rendering
Posted by "Alastair Maw (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alastair Maw updated WICKET-589:
--------------------------------
Assignee: Matej Knopp
> problem with Ajax and rendering
> -------------------------------
>
> Key: WICKET-589
> URL: https://issues.apache.org/jira/browse/WICKET-589
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Environment: wicket build from svn trunk revision 540588
> Reporter: Xavier Hanin
> Assignee: Matej Knopp
> Fix For: 1.3.0-rc1
>
>
> Problem description copied from the mailing list:
> After upgrading from wicket 1.3 beta 1 to a build based on revision 540588, I get the following error message:
> 18:49:19.245 [btpool0-2] ERROR org.apache.wicket.RequestCycle - The
> component(s) below failed to render. A common problem is that you have
> added a component in code but forgot to reference it in the markup
> (thus the component will never be rendered).
> 1. [MarkupContainer [Component id = progressBarStylesheet, page =
> org.xoocode.xooctory.web.pages.dashboard.Dashboard, path =
> 2:projects-panel:projects:6:leftTimePanel:progressBar:progressBarStylesheet.StyleSheetReference,
> isVisible = true, isVersioned = false]]
> The problem is that the component is properly added, and it worked
> before upgrading, so...
> So I've tried to track down the problem, and I've not found the source
> of the problem. As a workaround I disable check rendering with:
> getDebugSettings().setComponentUseCheck(false);
> Then everything works properly, and the component (a style sheet) is
> properly rendered.
> Let me explain a little bit more the situation in which the problem occurs.
> The component which is causing the problem is a StyleSheetReference
> added to a panel. The markup contains the corresponding link in a
> wicket:head section.
> The panel is invisible when the page is loaded, but then I use an ajax
> link to trigger an action, which later triggers the visibility of this
> component to true. Then this component is refreshed by an AjaxTimer
> (actually I use wicket-contrib-push, but I don't think it really makes
> a difference, since it's using a simple AbstractAjaxTimerBehavior
> underneath). And that's when the component is rendered that the check
> rendering is failing. Some analysis shown that there's a
> StyleSheetReference with the good id in the renderedComponent
> attribute of Page, but it isn't the exact same StyleSheetReference
> instance as the one checked by the checkRendering method. For the
> moment I haven't managed to really see why I have two instances, what
> doesn't help is that it seems that when I debug, the problem goes away
> depending on the occurence of other timer based ajax requests.
> For more details the sources are available here:
> ProgressBar.java
> http://www.xoocode.org/wsvn/xoocode/org.xoocode.xooctory/trunk/xooctory/src/main/java/org/xoocode/xooctory/web/component/ProgressBar.java?op=file&rev=189&sc=0
> ProgressBar.html
> http://www.xoocode.org/wsvn/xoocode/org.xoocode.xooctory/trunk/xooctory/src/main/java/org/xoocode/xooctory/web/component/ProgressBar.html?op=file&rev=166&sc=0
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-589) problem with Ajax and rendering
Posted by "Xavier Hanin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503389 ]
Xavier Hanin commented on WICKET-589:
-------------------------------------
I've upgraded to a version based on svn revision 546025 and I don't have the problem anymore. My code has changed so I can't be 100% sure the problem is fixed, but it's very likely it is, so I'm fine with closing this bug.
> problem with Ajax and rendering
> -------------------------------
>
> Key: WICKET-589
> URL: https://issues.apache.org/jira/browse/WICKET-589
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Environment: wicket build from svn trunk revision 540588
> Reporter: Xavier Hanin
> Assignee: Matej Knopp
> Fix For: 1.3.0-rc1
>
>
> Problem description copied from the mailing list:
> After upgrading from wicket 1.3 beta 1 to a build based on revision 540588, I get the following error message:
> 18:49:19.245 [btpool0-2] ERROR org.apache.wicket.RequestCycle - The
> component(s) below failed to render. A common problem is that you have
> added a component in code but forgot to reference it in the markup
> (thus the component will never be rendered).
> 1. [MarkupContainer [Component id = progressBarStylesheet, page =
> org.xoocode.xooctory.web.pages.dashboard.Dashboard, path =
> 2:projects-panel:projects:6:leftTimePanel:progressBar:progressBarStylesheet.StyleSheetReference,
> isVisible = true, isVersioned = false]]
> The problem is that the component is properly added, and it worked
> before upgrading, so...
> So I've tried to track down the problem, and I've not found the source
> of the problem. As a workaround I disable check rendering with:
> getDebugSettings().setComponentUseCheck(false);
> Then everything works properly, and the component (a style sheet) is
> properly rendered.
> Let me explain a little bit more the situation in which the problem occurs.
> The component which is causing the problem is a StyleSheetReference
> added to a panel. The markup contains the corresponding link in a
> wicket:head section.
> The panel is invisible when the page is loaded, but then I use an ajax
> link to trigger an action, which later triggers the visibility of this
> component to true. Then this component is refreshed by an AjaxTimer
> (actually I use wicket-contrib-push, but I don't think it really makes
> a difference, since it's using a simple AbstractAjaxTimerBehavior
> underneath). And that's when the component is rendered that the check
> rendering is failing. Some analysis shown that there's a
> StyleSheetReference with the good id in the renderedComponent
> attribute of Page, but it isn't the exact same StyleSheetReference
> instance as the one checked by the checkRendering method. For the
> moment I haven't managed to really see why I have two instances, what
> doesn't help is that it seems that when I debug, the problem goes away
> depending on the occurence of other timer based ajax requests.
> For more details the sources are available here:
> ProgressBar.java
> http://www.xoocode.org/wsvn/xoocode/org.xoocode.xooctory/trunk/xooctory/src/main/java/org/xoocode/xooctory/web/component/ProgressBar.java?op=file&rev=189&sc=0
> ProgressBar.html
> http://www.xoocode.org/wsvn/xoocode/org.xoocode.xooctory/trunk/xooctory/src/main/java/org/xoocode/xooctory/web/component/ProgressBar.html?op=file&rev=166&sc=0
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.