You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Andrea Aime (JIRA)" <ji...@apache.org> on 2008/08/03 11:01:44 UTC
[jira] Created: (WICKET-1769) AjaxPagingNavigation usare results in
AjaxPaginNavigator not found exception
AjaxPagingNavigation usare results in AjaxPaginNavigator not found exception
----------------------------------------------------------------------------
Key: WICKET-1769
URL: https://issues.apache.org/jira/browse/WICKET-1769
Project: Wicket
Issue Type: Bug
Components: wicket
Affects Versions: 1.3.4
Reporter: Andrea Aime
Fix For: 1.3.5, 1.4-M4
Using AjaxPagingNavigation causes the following stack trace:
{code}
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)
{code}
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?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (WICKET-1769) AjaxPagingNavigation usare results in
AjaxPaginNavigator not found exception
Posted by "Martijn Dashorst (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martijn Dashorst closed WICKET-1769.
------------------------------------
Resolution: Invalid
AjaxPagingNavigationBehavior is not intended to be used outside AjaxPagingNavigator.
> AjaxPagingNavigation usare results in AjaxPaginNavigator not found exception
> ----------------------------------------------------------------------------
>
> Key: WICKET-1769
> URL: https://issues.apache.org/jira/browse/WICKET-1769
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.4
> Reporter: Andrea Aime
> Fix For: 1.3.5, 1.4-M4
>
>
> Using AjaxPagingNavigation causes the following stack trace:
> {code}
> 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)
> {code}
> 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?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-1769) AjaxPagingNavigation usare results in
AjaxPaginNavigator not found exception
Posted by "Frank Bille Jensen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Frank Bille Jensen updated WICKET-1769:
---------------------------------------
Fix Version/s: (was: 1.4-RC1)
(was: 1.3.5)
> AjaxPagingNavigation usare results in AjaxPaginNavigator not found exception
> ----------------------------------------------------------------------------
>
> Key: WICKET-1769
> URL: https://issues.apache.org/jira/browse/WICKET-1769
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.4
> Reporter: Andrea Aime
>
> Using AjaxPagingNavigation causes the following stack trace:
> {code}
> 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)
> {code}
> 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?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.