[
https://issues.apache.org/jira/browse/WICKET-2461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Vaynberg resolved WICKET-2461.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.5-M1
1.4.2
Assignee: Igor Vaynberg
> AjaxPagingNavigationIncrementLink does not work without AjaxPagingNavigator
> component
> -------------------------------------------------------------------------------------
>
> Key: WICKET-2461
> URL: https://issues.apache.org/jira/browse/WICKET-2461
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.4.2
> Reporter: Andrej Thiele
> Assignee: Igor Vaynberg
> Priority: Minor
> Fix For: 1.4.2, 1.5-M1
>
>
> If the AjaxPagingNavigationIncrementLink should be use with a pagable
> component without the AjaxPagingNavigator then a WicketRuntimeException is
> thrown when the link is clicked. The documentation says:
> "
> An incremental Ajaxian link to a page of a PageableListView. Assuming your
> list view navigation looks like
>
> [first / << / <] 1 | 2 | 3 [> / >> /last]
>
> and "<" meaning the previous and "<<" goto the "current page - 5", than it is
> this kind of incremental page links which can easily be created. This link
> will update the pageable and itself or the navigator the link is part of
> using Ajax techniques, or perform a full refresh when ajax is not available.
> "
> From that description I understand, that the
> AjaxPagingNavigationIncrementLink component should work without a
> AjaxPagingNavigator too, like the non Ajax variant
> PagingNavigationIncrementLink.
> Reason for this is the implementation of the AjaxPagingNavigationBehavior
> which explicitly searches for the navigator component and throws the
> exception.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
