[
https://issues.apache.org/jira/browse/SLING-5468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15140961#comment-15140961
]
Konrad Windszus commented on SLING-5468:
----------------------------------------
My point from http://www.mail-archive.com/[email protected]/msg53814.html
was that if you are able to hide the local property through setting the
property {{sling:hideProperties}} you can also just not set the property you
want to hide on the local resource in the first place.
This would always be feasible except for the case where that property would be
used for resource merging itself. This is only the case for
{{sling:resourceSuperType}} so far (for the overriding picker).
You are right though that this is a change in behaviour, but I would argue if
someone would have relied on that IMHO buggy behaviour he can
a) easily fix that
b) should not have done so in the first place
The problem really is that there is no documentation really stating how it was
supposed to work, but I think I clearly stated that currently we have a
convincing use case for changing the behaviour -> disabling inheritance, while
on the other hand we only have a hardly convincing use case for keeping the
behaviour as is (hiding the resource super type in case you are using the
overriding picker).
Would you prefer introducing another special property instead to disable
inheritance?
> Resource Merger: Provide a way to completely replace the underlying resources
> -----------------------------------------------------------------------------
>
> Key: SLING-5468
> URL: https://issues.apache.org/jira/browse/SLING-5468
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Affects Versions: Resource Merger 1.2.10
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Fix For: Resource Merger 1.3.2
>
> Attachments: SLING-5468-v1.patch
>
>
> Currently whenever the mount point of the {{MergingResourcePicker}}
> (/mnt/overlay) or {{OverridingResourcePicker}} (/mnt/override) is used, the
> merging always takes place. It is only possible to hide/modify individual
> resource/properties of the underlying resources but not to completely disable
> the inheritance (and by that replace the whole overriden/overlaid resource).
> A concrete usecase for that is in a CMS (e.g. AEM) where the dialog
> definitions are always loaded via /mnt/override/<resource type>. In that case
> it is not easily possible to completely replace the dialog of the resource
> super type (as only individual child resources or properties can be hidden
> but there is no special property to ignore the inherited resource
> alltogether).
> I propose the following:
> Add a new property {{sling:disregardInheritedResource=true}} in which case
> all the inherited resources would not be taken into account for merging.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
