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

Frank Hölting commented on FELIX-5693:
--------------------------------------

1. Console log:
I suspect hereConfigurationAdminImpl#187

Bundle - org.apache.felix.configadmin:1.9.0.SNAPSHOT
 Service - 
{org.osgi.service.cm.ConfigurationAdmin}={service.description=Configuration 
Admin Service Specification 1.6 Implementation, service.id=59, 
service.bundleid=7, service.scope=bundle, service.vendor=The Apache Software 
Foundation, service.pid=org.apache.felix.cm.ConfigurationAdmin}
  DEBUG - 
listConfigurations(filter=(|(service.factoryPid=org.jcommand.executor.ExecutorComponent)(service.factoryPid=org.jcommand.executor.ExecutorComponent|org.jcommand.threadpool)(service.factoryPid=org.jcommand.executor.ExecutorComponent|org.jcommand.threadpool|1.0.0.201709221501)(service.factoryPid=org.jcommand.executor.ExecutorComponent|org.jcommand.threadpool|1.0.0.201709221501|reference:file:/home/frank/dev/jcommand-master/git/jcommand/bundles/org.jcommand.threadpool/generated/org.jcommand.threadpool.jar)))
 -> 17:01:53.753
  DEBUG - Listing configurations matching 
(|(service.factoryPid=org.jcommand.executor.ExecutorComponent)(service.factoryPid=org.jcommand.executor.ExecutorComponent|org.jcommand.threadpool)(service.factoryPid=org.jcommand.executor.ExecutorComponent|org.jcommand.threadpool|1.0.0.201709221501)(service.factoryPid=org.jcommand.executor.ExecutorComponent|org.jcommand.threadpool|1.0.0.201709221501|reference:file:/home/frank/dev/jcommand-master/git/jcommand/bundles/org.jcommand.threadpool/generated/org.jcommand.threadpool.jar))
 -> 17:01:53.753
  DEBUG - 
listConfigurations(filter=(|(service.pid=org.jcommand.executor.ExecutorComponent)(service.pid=org.jcommand.executor.ExecutorComponent|org.jcommand.threadpool)(service.pid=org.jcommand.executor.ExecutorComponent|org.jcommand.threadpool|1.0.0.201709221501)(service.pid=org.jcommand.executor.ExecutorComponent|org.jcommand.threadpool|1.0.0.201709221501|reference:file:/home/frank/dev/jcommand-master/git/jcommand/bundles/org.jcommand.threadpool/generated/org.jcommand.threadpool.jar)))
 -> 17:01:53.754
  DEBUG - Listing configurations matching 
(|(service.pid=org.jcommand.executor.ExecutorComponent)(service.pid=org.jcommand.executor.ExecutorComponent|org.jcommand.threadpool)(service.pid=org.jcommand.executor.ExecutorComponent|org.jcommand.threadpool|1.0.0.201709221501)(service.pid=org.jcommand.executor.ExecutorComponent|org.jcommand.threadpool|1.0.0.201709221501|reference:file:/home/frank/dev/jcommand-master/git/jcommand/bundles/org.jcommand.threadpool/generated/org.jcommand.threadpool.jar))
 -> 17:01:53.754

2. immediate = true
That's a little surprising. I wasn't aware that a lazy DS component would be 
deactivated if there was no more service reference. immediate worked. Thank 
you. Thank you.
I have to take the Spec. read.

>From my point of view the version1.9.0-SNAPSHOT works then.

> 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