[
https://issues.apache.org/jira/browse/SYNCOPE-829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15324553#comment-15324553
]
fabio martelli commented on SYNCOPE-829:
----------------------------------------
Unfortunately not all the connectors seem to implement the pagination feature
in the same way (someone does not implement it at all).
LDAP connector, for instance, does not permit to implement "prev" request
because the pagination cookie dos not change page by page.
Currently we will just provide the possibility to browse resource connector
objects page by page, from the first page to the last one, without the
possibility to go back.
> Use actual pagination for resource explore
> ------------------------------------------
>
> Key: SYNCOPE-829
> URL: https://issues.apache.org/jira/browse/SYNCOPE-829
> Project: Syncope
> Issue Type: Improvement
> Components: console
> Reporter: Francesco Chicchiriccò
> Assignee: fabio martelli
> Fix For: 2.0.0
>
>
> The feature introduced by SYNCOPE-789 uses Wicket's {{AjaxDataTable}} and
> {{DataProvider}} so requires, for pagination implementation, the total number
> of items to show being known upfront.
> Unfortunately, the result from {{ResourceService#listConnObjects}} cannot
> contain such information - due to the way how the underlying search is
> implemented in ConnId - so at the moment the console code stores all items
> (up to 100 maximum as temporary protection) in memory and then paginates from
> there.
> This is natural suboptimal: what is required is to provide a different Wicket
> component (ideally a {{ListView}})) which will not provide full pagination
> features but only {{next}} and {{prev}} buttons, more adherent to the
> underlying data.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
