[
https://issues.apache.org/jira/browse/SLING-6293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert resolved SLING-6293.
-----------------------------------
Resolution: Fixed
Completed: At revision: 1770249
(!) please note: this change broke the backward compatibility of the SPI
package {{org.apache.sling.caconfig.resource.spi}}, because i required two new
methods and a minor contract change of an existing methods in the interface
ConfigurationResourceResolvingStrategy.
this is required for this ticket, and for SLING-6137 as well.
this i had to increase package version of
{{org.apache.sling.caconfig.resource.spi}} to 2.0.0. i assume there are not yet
many implementations of this interface out there, implementors of other
interfaces in this packages have just to recompile with the lastest version.
fyi, [~cziegeler]
> 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.1.2, Context-Aware
> Configuration Impl 1.1.2
>
>
> 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)
