[
https://issues.apache.org/jira/browse/SLING-6114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15555362#comment-15555362
]
Stefan Seifert commented on SLING-6114:
---------------------------------------
proposal: https://github.com/apache/sling/pull/179
some remarks:
* implementation works as described above including the special usecase
* i saw that the your assumption from the ticket description which i answered
in [this
comment|https://issues.apache.org/jira/browse/SLING-6114?focusedCommentId=15555129#comment-15555129]
was somewhat implemented already at least how the osgi config was defined
previously:
** it defined allowed path /conf, /apps/conf, /libs/conf - with any path
hierarchy
** so it would be possible to store deep hierarchy of config below /apps/conf
and /libs/conf for this whitelist, although the remaining implementation did
not support this
** and it would be possible for a content resource to reference a config
resource below or equals /apps/conf and /libs/conf and /conf/global directly,
which should not be the case in my opinion - these are only fallback path, and
referencing a global config directly makes no sense when using context-aware
config without any context
* so i changed the implementation to allow only one single (configurable) path
where configuration are stored in (default: /conf), and allowing only
references to resources below this path (i will update the PR to disallow
references to /conf/global) as well.
[~cziegeler] what is your opinion on this whitelist/reference aspect?
> 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)
