[
https://issues.apache.org/jira/browse/SLING-3657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14027663#comment-14027663
]
Gilles Knobloch edited comment on SLING-3657 at 6/11/14 11:54 AM:
------------------------------------------------------------------
[~justinedelson]: got it, fair enough
I initially didn't think about a custom root path for #2, but more something
like {{ResourceMergerService.mergeSuperTypes(Resource r)}} (or whatever better
method name)
Anyway, some methods like {{ResourceMergerService.getMergedResource(Resource
r)}} should probably be extended to use the desired mount path, and therefore
corresponding overriding method. Something like
{{ResourceMergerService.getMergedResource(Resource r,
ResourceMergerService.OVERLAY | ResourceMergerService.OVERRIDE)}}
was (Author: gknob):
[~justinedelson]: got it, fair enough
I initially didn't think about a custom root path for #2, but more something
like {{ResourceMergerService.mergeSuperTypes(Resource r}} (or whatever better
method name)
Anyway, some methods like {{ResourceMergerService.getMergedResource(Resource
r}} should probably be extended to use the desired mount path, and therefore
corresponding overriding method. Something like
{{ResourceMergerService.getMergedResource(Resource r,
ResourceMergerService.OVERLAY | ResourceMergerService.OVERRIDE)}}
> Create a ResourceMerger-style ResourceProvider which merges based on resource
> super types
> -----------------------------------------------------------------------------------------
>
> Key: SLING-3657
> URL: https://issues.apache.org/jira/browse/SLING-3657
> Project: Sling
> Issue Type: New Feature
> Components: Extensions
> Reporter: Justin Edelson
> Attachments: SLING-3657.patch
>
>
> The current MergingResourceProvider does a good job of a single use case -
> merging resources relative to the search paths. A second use case for merging
> is to merge resources based on their sling:resourceSuperType inheritance, i.e.
> /content/siteA@sling:resourceSuperType=/content/siteB
> /content/siteB@sling:resourceSuperType=/content/siteC
> It should be possible to generate a merged resource which combines
> /content/siteA, /content/siteB, and /content/siteC (in reverse order so that
> siteA overrides siteB, etc.).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
