You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Alec Swan <al...@gmail.com> on 2010/11/23 18:58:22 UTC
WicketRuntimeException: component not found on page
Hello,
We upgraded our app to use Wicket 1.4.13. After that we started getting
sporadic WicketRuntimeExceptions about components not being found on a some
pages. We made changes to some, but not all pages, which exhibit this
behavior. Has anyone else noticed this with 1.4.14? Any ideas on how to
troubleshoot this intermittent behavior?
Here is an example:
microSitePanel:mainMenuContentPanel:secondMenuItem:1:secondMenuItemLink not
found on page
com.galecsy.lrm.web.wicket.offer.OfferManagementPage[id = 1], listener
interface =
[RequestListenerInterface name=IBehaviorListener, method=public abstract
void
org.apache.wicket.behavior.IBehaviorListener.onRequest()]
at
org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequestCycleProcessor.java:26
Thanks
Re: WicketRuntimeException: component not found on page
Posted by Igor Vaynberg <ig...@gmail.com>.
start by creating a quickstart that reproduces it so we can better understand it
-igor
On Tue, Nov 23, 2010 at 9:38 PM, Alec Swan <al...@gmail.com> wrote:
> I noticed that all "component not found on page" exceptions were
> thrown for AjaxEditableLabel and AjaxLink components located inside of
> a DataView.
>
> It seems like other people had a "component not found on page" problem
> inside of DataView components:
> http://www.mail-archive.com/users@wicket.apache.org/msg08636.html
> http://apache-wicket.1842946.n4.nabble.com/component-not-found-on-page-for-a-Link-colun-in-the-Datatable-after-self-refresh-using-the-AjaxSelfUr-td1892913.html#a2229885
>
> A workaround in JIRA 923 recommends turn off browser caching to solve
> "component not found on page" problem when using the Back button.
> However, in my case the Back button is not used, instead the DataView
> is refreshed using Ajax.
>
> Could anybody provide any suggestions on how to fix this problem?
>
> Thanks
>
> On Tue, Nov 23, 2010 at 10:58 AM, Alec Swan <al...@gmail.com> wrote:
>>
>> Hello,
>>
>> We upgraded our app to use Wicket 1.4.13. After that we started getting sporadic WicketRuntimeExceptions about components not being found on a some pages. We made changes to some, but not all pages, which exhibit this behavior. Has anyone else noticed this with 1.4.14? Any ideas on how to troubleshoot this intermittent behavior?
>>
>> Here is an example:
>>
>> microSitePanel:mainMenuContentPanel:secondMenuItem:1:secondMenuItemLink not found on page
>> com.galecsy.lrm.web.wicket.offer.OfferManagementPage[id = 1], listener interface =
>> [RequestListenerInterface name=IBehaviorListener, method=public abstract void
>> org.apache.wicket.behavior.IBehaviorListener.onRequest()]
>> at
>> org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequestCycleProcessor.java:26
>>
>> Thanks
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: WicketRuntimeException: component not found on page
Posted by Alec Swan <al...@gmail.com>.
I noticed that all "component not found on page" exceptions were
thrown for AjaxEditableLabel and AjaxLink components located inside of
a DataView.
It seems like other people had a "component not found on page" problem
inside of DataView components:
http://www.mail-archive.com/users@wicket.apache.org/msg08636.html
http://apache-wicket.1842946.n4.nabble.com/component-not-found-on-page-for-a-Link-colun-in-the-Datatable-after-self-refresh-using-the-AjaxSelfUr-td1892913.html#a2229885
A workaround in JIRA 923 recommends turn off browser caching to solve
"component not found on page" problem when using the Back button.
However, in my case the Back button is not used, instead the DataView
is refreshed using Ajax.
Could anybody provide any suggestions on how to fix this problem?
Thanks
On Tue, Nov 23, 2010 at 10:58 AM, Alec Swan <al...@gmail.com> wrote:
>
> Hello,
>
> We upgraded our app to use Wicket 1.4.13. After that we started getting sporadic WicketRuntimeExceptions about components not being found on a some pages. We made changes to some, but not all pages, which exhibit this behavior. Has anyone else noticed this with 1.4.14? Any ideas on how to troubleshoot this intermittent behavior?
>
> Here is an example:
>
> microSitePanel:mainMenuContentPanel:secondMenuItem:1:secondMenuItemLink not found on page
> com.galecsy.lrm.web.wicket.offer.OfferManagementPage[id = 1], listener interface =
> [RequestListenerInterface name=IBehaviorListener, method=public abstract void
> org.apache.wicket.behavior.IBehaviorListener.onRequest()]
> at
> org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequestCycleProcessor.java:26
>
> Thanks
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org