Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
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.).