You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2016/11/02 10:23:58 UTC
[jira] [Commented] (SLING-6229) Allow configuration of fallback
properties in DefaultContextPathStrategy
[ https://issues.apache.org/jira/browse/SLING-6229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15628494#comment-15628494 ]
Carsten Ziegeler commented on SLING-6229:
-----------------------------------------
Implemented in rev 1767627
[~sseifert@pro-vision.de] WDYT?
> Allow configuration of fallback properties in DefaultContextPathStrategy
> ------------------------------------------------------------------------
>
> Key: SLING-6229
> URL: https://issues.apache.org/jira/browse/SLING-6229
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: Context-Aware Configuration Impl 1.0.0
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Context-Aware Configuration Impl 1.0.2
>
>
> Currently the DefaultContextPathStrategy only looks for the property sling:configRef.
> If other properties should be looked for, e.g. for migration from Adobe's confmgr, this can be done with an additional ContextPathStrategy - but this has a performance drawback.
> We should allow to define additional property names which are used in the order of appearance. Once a value for such a property is found, its value is used and the others are not queried anymore. The sling:configRef property is always the first one used and does not need to be configured - which also means it is not possible to deviate from this rule.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)