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/04/08 17:40:25 UTC

[jira] [Created] (SYNCOPE-829) Use actual pagination for resource explore

Francesco Chicchiriccò created SYNCOPE-829:
----------------------------------------------

             Summary: 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ò
             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)