[
https://issues.apache.org/jira/browse/SLING-6336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15702706#comment-15702706
]
Radu Cotescu commented on SLING-6336:
-------------------------------------
Thanks for the pointer! I guess I like your implementations more than what I've
pushed in [r1771782|https://svn.apache.org/r1771782], because you also make
sure to wrap the returned resources. In this case I wanted to implement the
wrapper so that consumers that decide to implement their own resource resolver
are not forced to import {{org.apache.sling.api.resource}} with a minor-limited
import range. Such an example is the {{ScriptingResourceResolverProvider}} from
SLING-6165 that needs to provide a slightly modified {{ResourceResolver}}.
[~fmeschbe], [~jsedding], should we revise the patches from the issues Julian
mentioned and merge them with what I pushed?
> Implement a ResourceResolverWrapper
> -----------------------------------
>
> Key: SLING-6336
> URL: https://issues.apache.org/jira/browse/SLING-6336
> Project: Sling
> Issue Type: Improvement
> Components: API
> Reporter: Radu Cotescu
> Assignee: Radu Cotescu
> Fix For: API 2.15.2
>
>
> A {{ResourceResolverWrapper}} would help consumers who implement the
> {{ResourceResolver}} interface to not define restrictive import ranges for
> the {{org.apache.sling.api.resource}} API package.
> The implementation should delegate all calls to the wrapped resource
> resolver, similar to the {{ResourceWrapper}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
