[
https://issues.apache.org/jira/browse/SLING-1873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14541737#comment-14541737
]
Santiago García Pimentel edited comment on SLING-1873 at 5/13/15 11:17 AM:
---------------------------------------------------------------------------
What would be a nice way of solving this? I havent' fully checked the source
code, but from top of my head, I think the resourceresolver could be extended
to overload findResources() to receive extra parameters for limit and offset,
which then would be set to the Query object before executing.
But maybe this should belong in a new Class (which could be adapted from the
resolver)
What do you think?
was (Author: santiagozky):
What would be a nice way of solving this? I havent' fully checked the source
code, but from top of my head, I think the resourceresolver could be extended
to overload findResources() to receive extra parameters for limit and offset,
which then would be set to the Query object before executing.
Would that be acceptable?
> Overload ResourceResolver.findResources to allow for query options such as
> limit, offset
> ----------------------------------------------------------------------------------------
>
> Key: SLING-1873
> URL: https://issues.apache.org/jira/browse/SLING-1873
> Project: Sling
> Issue Type: Improvement
> Components: JCR
> Reporter: Sarwar Bhuiyan
>
> I've found the resourceResolver.findResources(query, language) to be quite
> convenient in circumstances where we run a lot of searches. It would be
> convenient to be able to set the Query limit and offset in this method so
> that it can make use of the JCR 2 features where our result sets can get
> quite big.
> Thanks.
> Sarwar
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
