You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Justin Edelson (JIRA)" <ji...@apache.org> on 2014/11/29 16:47:14 UTC

[jira] [Closed] (SLING-3657) Create a ResourceMerger-style ResourceProvider which merges based on resource super types

     [ https://issues.apache.org/jira/browse/SLING-3657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Edelson closed SLING-3657.
---------------------------------

> 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
>            Assignee: Justin Edelson
>             Fix For: Resource Merger 1.2.0
>
>         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.3.4#6332)