You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by Konrad Windszus <ko...@netcentric.biz> on 2016/01/29 11:46:02 UTC
Superimposing resource resolver
Hi,
IMHO the superimposing resource resolver can be deprecated now (https://issues.apache.org/jira/browse/SLING-1778) as now the overriding resource merger is available (https://issues.apache.org/jira/browse/SLING-3657).
Although the latter uses sling:resourceSuperType instead of sling:superimposeSourcePath everything can be done with the resource merger and it is even more flexible.
WDYT about removing the bundle https://svn.apache.org/repos/asf/sling/trunk/contrib/extensions/superimposing?
Konrad
RE: Superimposing resource resolver
Posted by Stefan Seifert <ss...@pro-vision.de>.
there are projects in production out there using this bundle, so we should not just remove it. sling resource merger is not a drop-in replacement, i've not checked in detail if really all usecases of the superimposing resource provider can be replaced with it.
we should start adding a prominent notice to the documentation of the superimposing resource to provider to look first to the resource merge because it is more flexible and better maintained.
stefan
>-----Original Message-----
>From: Konrad Windszus [mailto:konrad.windszus@netcentric.biz]
>Sent: Friday, January 29, 2016 11:46 AM
>To: dev@sling.apache.org
>Subject: Superimposing resource resolver
>
>Hi,
>IMHO the superimposing resource resolver can be deprecated now
>(https://issues.apache.org/jira/browse/SLING-1778) as now the overriding
>resource merger is available (https://issues.apache.org/jira/browse/SLING-
>3657).
>Although the latter uses sling:resourceSuperType instead of
>sling:superimposeSourcePath everything can be done with the resource merger
>and it is even more flexible.
>WDYT about removing the bundle
>https://svn.apache.org/repos/asf/sling/trunk/contrib/extensions/superimposi
>ng?
>
>Konrad
Re: Superimposing resource resolver
Posted by Konrad Windszus <ko...@netcentric.biz>.
Actually there is one section in https://github.com/apache/sling/blob/trunk/contrib/extensions/superimposing/README.md#comparison-with-sling-resource-merger <https://github.com/stefanseifert/sling-superimposing#comparison-with-sling-resource-merger> mentioning why both are necessary, but that section only considers the MergingResourcePicker (/mnt/overlay) not the newer OverridingResourcePicker (/mnt/override).
> On 29 Jan 2016, at 11:46, Konrad Windszus <ko...@netcentric.biz> wrote:
>
> Hi,
> IMHO the superimposing resource resolver can be deprecated now (https://issues.apache.org/jira/browse/SLING-1778) as now the overriding resource merger is available (https://issues.apache.org/jira/browse/SLING-3657).
> Although the latter uses sling:resourceSuperType instead of sling:superimposeSourcePath everything can be done with the resource merger and it is even more flexible.
> WDYT about removing the bundle https://svn.apache.org/repos/asf/sling/trunk/contrib/extensions/superimposing?
>
> Konrad