[jira] [Resolved] (SLING-6114) Support nested configurations in configurated locations

["Stefan Seifert (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-6114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Seifert resolved SLING-6114.
-----------------------------------
    Resolution: Fixed

Completed: At revision: 1763789  


> Support nested configurations in configurated locations
> -------------------------------------------------------
>
>                 Key: SLING-6114
>                 URL: https://issues.apache.org/jira/browse/SLING-6114
>             Project: Sling
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Carsten Ziegeler
>            Assignee: Stefan Seifert
>              Labels: contextaware-config
>             Fix For: Context-Aware Configuration 1.0.0
>
>
> 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?



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