[ https://issues.apache.org/jira/browse/SLING-3657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14027829#comment-14027829 ]
Antonio Sanso commented on SLING-3657: -------------------------------------- I am out of office, back on June 22. regards antonio > 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)