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
- relates to
-
SYNCOPE-789 Browse objects on external resources
- Closed