Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Invalid
-
1.3.4
-
None
-
None
Description
Using AjaxPagingNavigation causes the following stack trace:
org.apache.wicket.WicketRuntimeException: Unable to find AjaxPagingNavigator component in hierarchy starting from [MarkupContainer [Component id = pageLink, page = org.geoserver.HomePage, path = 0:navigator:fileBrowser:navigation:1:pageLink.AjaxPagingNavigationLink, isVisible = true, isVersioned = true]] at org.apache.wicket.ajax.markup.html.navigation.paging.AjaxPagingNavigationBehavior.onEvent(AjaxPagingNavigationBehavior.java:82) at org.apache.wicket.ajax.AjaxEventBehavior.respond(AjaxEventBehavior.java:161) at org.apache.wicket.ajax.AbstractDefaultAjaxBehavior.onRequest(AbstractDefaultAjaxBehavior.java:293) at org.apache.wicket.request.target.component.listener.BehaviorRequestTarget.processEvents(BehaviorRequestTarget.java:100) at org.apache.wicket.request.AbstractRequestCycleProcessor.processEvents(AbstractRequestCycleProcessor.java:91) at org.apache.wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:1166) at org.apache.wicket.RequestCycle.step(RequestCycle.java:1243) at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1331) at org.apache.wicket.RequestCycle.request(RequestCycle.java:493) at org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:363) at org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:194)
This is due to AjaxPagingNavigationBehaviour looking for a AjaxPaging navigator instead of the navigation. I'm confused, is the AjaxPagingNavigation not supposed to be used directly, or is this a bug in the behaviour?