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/10/18 07:58:58 UTC
[jira] [Closed] (SLING-6152) Context-Aware Config: Config reference
should be detected in ContextPathStrategy
[ https://issues.apache.org/jira/browse/SLING-6152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler closed SLING-6152.
-----------------------------------
> Context-Aware Config: Config reference should be detected in ContextPathStrategy
> --------------------------------------------------------------------------------
>
> Key: SLING-6152
> URL: https://issues.apache.org/jira/browse/SLING-6152
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: Context-Aware Configuration API 1.0.0
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
> Labels: contextaware-config
> Fix For: Context-Aware Configuration SPI 1.0.0, Context-Aware Configuration Impl 1.0.0
>
>
> currently the DefaultContextPathStrategy checks for the availability of the sling:config-ref prop, but it does not return it's value, this is done in the DefaultConfigurationResourceResolvingStrategy.
> this is as bit inconsistent, leading to configure the lookup of SLING-6149 in multiple places, and makes it more difficult to define scenarios where the config references is build on a conventions-based pattern (e.g. derived from content path) instead of an explicit sling:config-ref property.
> the logic itself and other implementation details of both strategies remain untouched.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)