You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Julian Sedding (JIRA)" <ji...@apache.org> on 2016/01/29 17:23:39 UTC

[jira] [Comment Edited] (SLING-5468) Resource Merger: Provide a way to completely replace the underlying resources

    [ https://issues.apache.org/jira/browse/SLING-5468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15123682#comment-15123682 ] 

Julian Sedding edited comment on SLING-5468 at 1/29/16 4:22 PM:
----------------------------------------------------------------

[~kwin] can the same not be achieved by setting {{sling:hideProperties=\*}} and {{sling:hideChildren=\*}} on the node (e.g. dialog definition?)


was (Author: jsedding):
[~kwin] can the same not be achieved by setting {{sling:hideProperties=*}} and {{sling:hideChildren=*}} on the node (e.g. dialog definition?)

> 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
>
> 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)