[ https://issues.apache.org/jira/browse/SLING-3657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14027642#comment-14027642 ]
Gilles Knobloch commented on SLING-3657: ---------------------------------------- Thanks for the patch [~justinedelson]. I'm actually wondering why this needs to be another mount patch. I'd rather see (0) resurrected as part of SLING-3423. (0) https://github.com/gknob/sling-resourcemerger/commit/a3e1b78c87e54cd5c32a58627a4de0420229e1f9 > 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)