Uploaded image for project: 'Syncope'
  1. Syncope
  2. SYNCOPE-829

Use actual pagination for resource explore

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 2.0.0-M4
    • console
    • None

    Description

      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.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            fmartelli Fabio Martelli
            ilgrosso Francesco Chicchiriccò
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment