[
https://issues.apache.org/jira/browse/SLING-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885384#comment-13885384
]
Carsten Ziegeler commented on SLING-2986:
-----------------------------------------
I've fixed some path handling within the provider and also fixed the metadata
handling (always a new object was created)
I'm not happy with the resource type returned by the merged resource : in the
best case, the merged resources have the same resource type, so we could simply
return this. And as the resources are merged, their properties are merged and
therefore sling:resourceType is merged as well, so we could also return this.
[~gknob] Is there any reason/use case for returning the relative path as
resource type?
> Merged Resource Provider
> ------------------------
>
> Key: SLING-2986
> URL: https://issues.apache.org/jira/browse/SLING-2986
> Project: Sling
> Issue Type: New Feature
> Components: Extensions
> Reporter: Gilles Knobloch
> Assignee: Carsten Ziegeler
> Fix For: Resource Merger 1.0.0
>
> 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)
