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

Carsten Ziegeler commented on FELIX-5693:
-----------------------------------------

[~fhoelting]
Re 1 : Who is doing this output? I couldn't find it in the configuration admin 
code.
Re patch : This is a consequence of you using DS - you're component is lazy and 
therefore gets activated/deactivated each time someone gets the service from 
the service reference. The configuration admin implementation is correct in 
getting/ungetting the service each time. There are a couple of ways to fix this 
with your DS component, making it immediate is one way.
Re 3 : If no config is found, null is passed into the update method.

> 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
>
>         Attachments: case1_with_felix.cm.pm.txt, 
> case2_without_felix.cm.pm.txt, 
> Differentiation-between-providing-the-config-and-rem.patch
>
>
> 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
(v6.4.14#64029)

Reply via email to