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/11/19 11:40:58 UTC
[jira] [Resolved] (SLING-6303) Context-Aware Config: Persisting
configuration resource collections with names
[ https://issues.apache.org/jira/browse/SLING-6303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Seifert resolved SLING-6303.
-----------------------------------
Resolution: Fixed
Fix Version/s: Context-Aware Configuration SPI 1.2.0
Completed: At revision: 1770484
i changed the interfaces of ConfigurationManager and ConfigurationPersistenceStrategy, that was the far cleaner solution.
(!) unfortunately i had to break the contract, raising major version to 2.0.0 for both.
[~cziegeler]: fyi
> Context-Aware Config: Persisting configuration resource collections with names
> ------------------------------------------------------------------------------
>
> Key: SLING-6303
> URL: https://issues.apache.org/jira/browse/SLING-6303
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: Context-Aware Configuration Impl 1.1.0
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
> Labels: contextaware-config
> Fix For: Context-Aware Configuration SPI 1.2.0, Context-Aware Configuration Impl 1.2.0
>
>
> currently the ConfigurationManager.persistCollection method allows to store configuration data. but i accepts only a collection of value map for each resource collection item, ignoring the name of each.
> but the name of each resource collection item is important e.g. for resource collection and property inheritance in resource collections, so application storing configuration data should be able to define a name for each as well.
> we either have to change the API for this, or define a magical property within the map to specfiy the name.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)