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 2019/06/20 15:44:00 UTC

[jira] [Resolved] (SLING-8526) Provide a Configuration PersistenceManager

     [ https://issues.apache.org/jira/browse/SLING-8526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved SLING-8526.
-------------------------------------
    Resolution: Fixed

Implemented in rev e3e69f1

if the framework property felix.cm.pm is set to featurelauncher, the launcher will register its own PM based on the memory PM and set the configurations from the feature model.

> Provide a Configuration PersistenceManager
> ------------------------------------------
>
>                 Key: SLING-8526
>                 URL: https://issues.apache.org/jira/browse/SLING-8526
>             Project: Sling
>          Issue Type: New Feature
>          Components: Feature Model
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>            Priority: Major
>             Fix For: Feature Model Launcher 1.0.6
>
>
> The Apache Felix configuration admin is configurable with persistence managers. We could provide our own persistence manager which stores configurations in memory and is initialized with the configurations from the provisioning model.
> This way, configurations from the provisioning model are instantly available when configuration admin comes up



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)