[SLING-6114] Support nested configurations in configurated locations

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: Context-Aware Configuration Impl 1.0.0
• Component/s: Extensions
• Labels: contextaware-config
• Assignee: Stefan Seifert
• Reporter: Carsten Ziegeler
• Created: 07/Oct/16 13:10
• Updated: 18/Oct/16 07:59
• Resolved: 07/Oct/16 15:36

Description

Let's assume you have a content like this:
/content/level1/level2[@sling-config-ref='/conf/project/sub']

and configurations
/conf/project/something
/conf/project/sub/something-else

the default path strategy should directly go up the hierarchy in the configured location (/conf in this case), so /conf/project/sub is tried first, then /conf/project and then the other configured paths.
The only question is if you have
/libs/conf/project/sub
is this handled before /conf/project or after?

Issue Links

• links to: GitHub Pull Request #179