[
https://issues.apache.org/jira/browse/SLING-6968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-6968:
-----------------------------------
Summary: Resource Merger: Add another resource picker which merges two
arbitrary resources given by path (was: Resource Merger: Add another resource
picker which explicitly merges two resources given by path)
> Resource Merger: Add another resource picker which merges two arbitrary
> resources given by path
> -----------------------------------------------------------------------------------------------
>
> Key: SLING-6968
> URL: https://issues.apache.org/jira/browse/SLING-6968
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: Resource Merger 1.3.4
> Reporter: Konrad Windszus
>
> Currently both resource pickers "overlay" and "override" shipped with the
> Sling Resource Merger determine only one resource from the given path url.
> The underlying/overlying resources are determined either via
> "sling:resourceSuperType" or via the resource resolver's search path.
> It would be useful to add a third resource picker which would allow to merge
> two explicitly specified resources (because both paths are given in the
> merged resource path).
> One concrete use case for that would be a composition pattern (in AEM: a
> dialog definition being composed out of multiple dialog definition child
> resources, being maintained somewhere in the repository but still allowing to
> overwrite some of the properties of the referenced dialog definition child
> resource).
> The only question is how to encode the two paths in the merged resource path
> (what to use as separator). One idea is to separate via ";". So the merged
> resource at {{/mnt/merge/<path1>;<path2>}} would merge the resource given at
> {{<path1>}} with the resource given at {{<path2>}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
