[SLING-6059] Context-Aware Config: Make resource inheritance for configuration collections configurable - ASF JIRA

Attach files

Attach Screenshot

Voters

Watch issue

Watchers

Create sub-task

Link

Clone

Update Comment Author

Replace String in Comment

Update Comment Visibility

Delete Comments

XML

Word

Printable

JSON

Details

Type: Improvement
Status: Closed
Priority: Major
Resolution: Fixed
Affects Version/s: None
Fix Version/s: Context-Aware Configuration Impl 1.0.0
Component/s: Extensions
Labels:
- contextaware-config

Description

currently and automatic merging/combining of configuration resource items takes place. example:

/conf/site1/feature/a
/conf/site1/feature/c
/conf/global/feature/b
/libs/conf/feature/c

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