felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Kriens (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FELIX-5693) Improve persistent manager handling
Date Thu, 21 Sep 2017 08:54:00 GMT

    [ https://issues.apache.org/jira/browse/FELIX-5693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16174461#comment-16174461

Peter Kriens commented on FELIX-5693:

Great! Thanks.

> Improve persistent manager handling
> -----------------------------------
>                 Key: FELIX-5693
>                 URL: https://issues.apache.org/jira/browse/FELIX-5693
>             Project: Felix
>          Issue Type: Improvement
>          Components: Configuration Admin
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: configadmin-1.9.0
> The current handling of persistence managers is a little bit fragile and not really deterministic.
> I propose the following enhancements:
> - Persistence managers can be registered with a "name" service property. The FilePersistenceManager
gets a name, e.g. "file"
> - we add a new framework property configuration - if that's empty or not there, CM acts
as today
> - if a value is configured, it's interpreted as a comma separated list of names. This
list of names makes up the PMs to be used by the implementation. All of them must be registered
and only these are used.
> - the PMs are used in the order they are specified in the list
> With this we have deterministic behaviour and full control while the default ootb behaviour
is still maintained. 

This message was sent by Atlassian JIRA

View raw message