[
https://issues.apache.org/jira/browse/SLING-6239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15636816#comment-15636816
]
Carsten Ziegeler commented on SLING-6239:
-----------------------------------------
A relative path is always resolved to the first absolute path, no matter if
there are other relative paths in between: For example:
/content/a
+ sling:confRef=/conf/a
/content/a/b
+ sling:confRef=b
/content/a/b/x
+ sling:confRef=x
will result in /conf/a/x for the resource /content/a/b/x
> Support relative references in DefaultConfigurationResourceResolvingStrategy
> ----------------------------------------------------------------------------
>
> Key: SLING-6239
> URL: https://issues.apache.org/jira/browse/SLING-6239
> Project: Sling
> Issue Type: New Feature
> Components: Extensions
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Context-Aware Configuration Impl 1.0.2
>
>
> If the value from the sling:confRef property is relative, the parent
> hierarchy of the context resource is traversed up to find a context
> resource with an absolute property. Once found, these are concatenated.
> For example
> /content/a
> + sling:confRef=/conf/a
> /content/a/b
> + sling:confRef=b
> If you try to find configurations for /content/a/b it searches in
> /conf/a/b first, then /conf/a
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
