I've just debugged and indeed problem is that there is no component with id "29". So clearly Wicket looks for an lazy "children" component from outdated DataView component.
Michal > -----Original Message----- > From: Michal Wegrzyn [mailto:michal.wegr...@onior.com] > Sent: Wednesday, November 02, 2011 16:11 > To: users@wicket.apache.org > Subject: RE: abort loading lazy components > > It is triggered when there is already new "itemList" (it extends > DataView), so I suppose that > PageAndComponentProvider looks for "itemList:29", which does not exists > anymore. > > Scenario: > > - Page is loaded but lazy components > ('folders:listContainer:itemList:itemPanel:folder:children') are still > loading > - User triggers folder change (itemList is replaced) > - Exception occurs > > If user triggers folder change when lazy components are completely > loaded (or during loading the last one) there is no exception at all. > > Best Regards, > Michal Wegrzyn > > -----Original Message----- > From: Martin Grigorov [mailto:mgrigo...@apache.org] > Sent: Wednesday, November 02, 2011 15:54 > To: users@wicket.apache.org > Subject: Re: abort loading lazy components > > On Wed, Nov 2, 2011 at 4:49 PM, Michal Wegrzyn > <michal.wegr...@onior.com> wrote: > > 15:32:24.028 user [http-8888-5] ERROR > o.a.wicket.DefaultExceptionMapper - Unexpected error occurred > > org.apache.wicket.request.handler.ComponentNotFoundException: Could > not find component > 'folders:listContainer:itemList:29:itemPanel:folder:children' on page > 'class package.MyPage > > Do you know how this is triggered ?
