You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Seifert (JIRA)" <ji...@apache.org> on 2016/12/19 12:01:58 UTC
[jira] [Closed] (SLING-6293) CAConfig: Separate SPI for Property
Inheritance
[ https://issues.apache.org/jira/browse/SLING-6293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Seifert closed SLING-6293.
---------------------------------
> CAConfig: Separate SPI for Property Inheritance
> -----------------------------------------------
>
> Key: SLING-6293
> URL: https://issues.apache.org/jira/browse/SLING-6293
> Project: Sling
> Issue Type: New Feature
> Components: Extensions
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
> Fix For: Context-Aware Configuration SPI 1.2.0, Context-Aware Configuration Impl 1.2.0
>
>
> currently, the property merging support is part of the DefaultConfigurationResourceResolvingStrategy, together with the support for resource collection merging.
> this conflicts with custom ConfigurationPersistenceStrategy which redirect the root resource e.g. to a {{jcr:content}} child node - property merging is broken then. by definition ConfigurationPersistenceStrategy does not has any knowledge of ConfigurationPersistenceStrategy's (they are on a "higher level" dedicated only to configurations).
> so the solution is to create a separate SPI for property merging, and apply it only to ConfigurationResolver and ConfigurationManager, not for the generic ConfigurationResourceResolver.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)