[
https://issues.apache.org/jira/browse/SLING-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13777272#comment-13777272
]
Carsten Ziegeler commented on SLING-2986:
-----------------------------------------
Thanks for the contribution, Gilles - I had a rough look and I'm wondering why
you introduce a new API for this. I would assume that a resource provider doing
the merging is all you need - apart from that the api reassembles me a little
bit of the collection api (though the intent is different of course).
For the implementation of the resource, the listChildren() method should be
implemented in the resource provider and the resource should just call the
resource resolver listChildren method (inherited from the abstract class). The
resource resolver than eventually calls the provider.
Before diving further into the implementation, I think we should first talk
about the API
> Merged Resource Provider
> ------------------------
>
> Key: SLING-2986
> URL: https://issues.apache.org/jira/browse/SLING-2986
> Project: Sling
> Issue Type: New Feature
> Components: ResourceResolver
> Reporter: Gilles Knobloch
>
> As exchanged once with Felix Meschberger, the idea is to implement a custom
> resource provider, with ability to merge multiple resources based on your
> search paths.
> For instance, if your search paths are
> /apps
> /libs
> Hitting /merge/my/resource/is/here will check
> /apps/my/resource/is/here
> /libs/my/resource/is/here
> There are some options like:
> - add/override property
> - delete a property of the resource under /libs
> - reorder nodes if available
> I intend to submit this patch as soon as possible.
> Code is currently located at https://github.com/gknob/sling-resourcemerger
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
