[
https://issues.apache.org/jira/browse/SLING-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gilles Knobloch updated SLING-2986:
-----------------------------------
Attachment: SLING-2986-WithService.zip
SLING-2986.zip
Sending two archives as patches:
* one without the Resource merger service
* one with the service
I agree it's not needed so far, but as mentioned by [~alexander.klimetschek],
it makes sense to have it if you want to use the mechanism at application level.
As we might need it anyway at one point, why not adding it from the beginning.
> 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
> Attachments: SLING-2986-WithService.zip, SLING-2986.zip
>
>
> 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.5#6160)
