[
https://issues.apache.org/jira/browse/SLING-6114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15555175#comment-15555175
]
Stefan Seifert commented on SLING-6114:
---------------------------------------
there is one special case - consider this scenario
{noformat}
/content/level1[@config-ref='/conf/a1/a2']
/content/level1/level2[@config-ref='/conf/b1/b2']
{noformat}
what is the expected lookup order for {{/content/level1/level2}}?
# {noformat}
/conf/b1/b2
/conf/b1
/conf/a1/a2
/conf/a1
/conf/global
/apps/conf
/libs/conf
{noformat}
# {noformat}
/conf/b1/b2
/conf/a1/a2
/conf/b1
/conf/a1
/conf/global
/apps/conf
/libs/conf
{noformat}
or asking other way around: which inheritance hierarchy has higher priority?
parent resources of the conf resources, or conf resources referenced by parent
resources of the content resource?
for me case #1 feels more sensible.
> 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)
