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

Stefan Seifert commented on SLING-6059:
---------------------------------------

i've renamed this ticket to make it configurable.

i think we should find a similar solution to control this inheritance as for 
property inheritance: SLING-6058

by default no inheritance takes place until it is enabled. having just a global 
switch "enable it globally yes/no" is too limiting, and would be to fearful to 
switch on for a system which makes intensive use of context-aware configuration.

perhaps a way to switch on the merging (of properties or resource collections) 
only for certain resources where it is required is the best option? e.g. a 
special property that enables this.

> Context-Aware Config: Make resource inheritance for configuration collections 
> configurable
> ------------------------------------------------------------------------------------------
>
>                 Key: SLING-6059
>                 URL: https://issues.apache.org/jira/browse/SLING-6059
>             Project: Sling
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Stefan Seifert
>            Assignee: Stefan Seifert
>              Labels: contextaware-config
>             Fix For: Context-Aware Configuration 1.0.0
>
>
> currently and automatic merging/combining of configuration resource items 
> takes place. example:
> {noformat}
> /conf/site1/feature/a
> /conf/site1/feature/c
> /conf/global/feature/b
> /libs/conf/feature/c
> {noformat}
> this returns a,b,c when config resource collection for "feature" is 
> requested. c is from /conf/site1/feature/c and not from /libs/conf/feature/c.
> this is inconsistent to the support for properties (where currently no such 
> "merging" is supported), and can have undesired effects.
> furthermore it is problematic when saving configuration collections via the 
> ConfigurationManager interface (SLING-6026). when storing a set of config 
> resources for /conf/site1 they are stored as children of /conf/site1/feature. 
> but when reading them again they are automatically merged with the others 
> from the fallback paths, and the user has no possibility to prevent this.
> so we should either disable this merging on paths, or implement it correctly 
> with giving the user control when merging should take place or not (confmgr 
> has a special property for this).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to