On 03.06.2015, at 14:52, Carsten Ziegeler <[email protected]> wrote: > Well, let's agree that we disagree here. For the majority of users, > there is only JCR anyway, which means there is no difference between > using a nice api and fiddling with strings by hand when it comes to > performance.
And that's exaclty the argument for not having a new query API that is agnostic to the individual resource provider implementations and would support aggregation. What's there with findResources() is fine - just do your jcr query there. Only passing offset/limit is missing. Cheers, Alex
