You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@syncope.apache.org by "Francesco Chicchiriccò (JIRA)" <ji...@apache.org> on 2016/06/13 09:53:21 UTC
[jira] [Resolved] (SYNCOPE-829) Use actual pagination for resource
explore
[ https://issues.apache.org/jira/browse/SYNCOPE-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francesco Chicchiriccò resolved SYNCOPE-829.
--------------------------------------------
Resolution: Fixed
The overall solution looks good to me, I have only moved the protection for the result size onto the query bean.
> 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)