sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler (JIRA)" <>
Subject [jira] [Updated] (SLING-4752) New resource query API
Date Wed, 04 Oct 2017 14:55:01 GMT


Carsten Ziegeler updated SLING-4752:
    Fix Version/s:     (was: Resource Resolver 1.5.32)
                       (was: JCR Resource 3.0.6)
                       (was: API 2.16.4)

> New resource query API
> ----------------------
>                 Key: SLING-4752
>                 URL:
>             Project: Sling
>          Issue Type: Improvement
>          Components: API, JCR, ResourceResolver
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>         Attachments: api-patch.txt, resourceresolver-patch.txt
> Discussion thread:
> Starting mail:
> The current resource query api has several problems:
> - it's using the JCR spec to define a query
> - it's not clear which queries are supported by providers
> - queries are string based
> - implementing queries in a resource provider is way too hard as this
> would require to implement the complete jcr query api.
> I've created a draft for a new, object based API at [1]. The main idea
> is to use a builder pattern to create Query objects. This are immutable
> and have a unique identifier. The QueryManager service can be used to
> execute a query in the context of a resource resolver. The manager
> delegates the query to the providers. As each Query object has this
> identifier, implementations can use this to cache the parsing of the query.
> In addition to the query object you can pass in query instructions to
> specify a limit or range for the query.
> Obviously this is a reduced set compared to the full fledged jcr search
> api, however it should be suitable for the majority of use cases.
> [1]

This message was sent by Atlassian JIRA

View raw message