You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Gilles Knobloch (JIRA)" <ji...@apache.org> on 2013/10/25 12:28:33 UTC
[jira] [Comment Edited] (SLING-2986) Merged Resource Provider
[ https://issues.apache.org/jira/browse/SLING-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13805207#comment-13805207 ]
Gilles Knobloch edited comment on SLING-2986 at 10/25/13 10:28 AM:
-------------------------------------------------------------------
[~jsedding], I logged issues (and fixed) for both of your comments:
* https://github.com/gknob/sling-resourcemerger/issues/9
* https://github.com/gknob/sling-resourcemerger/issues/10
was (Author: gknob):
[~jsedding], I adressed both of your comments:
* https://github.com/gknob/sling-resourcemerger/issues/9
* https://github.com/gknob/sling-resourcemerger/issues/10
> 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 was sent by Atlassian JIRA
(v6.1#6144)