[
https://issues.apache.org/jira/browse/SLING-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13881489#comment-13881489
]
Alexander Klimetschek commented on SLING-2986:
----------------------------------------------
We have a use case already: a UI definition in a resource type would be able to
extend one from a super resource type. The specifics of the child node that
makes up the UI definition in the resource type node are up to the application,
and the paths passed in the resource merger service would be the resource type
hierarchy.
The whole point of making this a service was to share the same logic for both
the special resource provider (which is just one use case) and other
application level "extension" mechanisms as the one above.
> 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)
