[
https://issues.apache.org/jira/browse/FELIX-6059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16861375#comment-16861375
]
Carsten Ziegeler commented on FELIX-6059:
-----------------------------------------
I've started to implement the second part in rev 1861069.
A framework property named "felix.cm.config.plugins" can be configured with a
comma separated list of names and if so, configuration plugins with the
"config.plugin.id" property matching those names have to be registered.
Otherwise the configuration admin is never registered as a service.
The implementation propably needs more testing
The first part needs to be implemented as well
> Improve usability for ConfigurationPlugins
> ------------------------------------------
>
> Key: FELIX-6059
> URL: https://issues.apache.org/jira/browse/FELIX-6059
> Project: Felix
> Issue Type: Improvement
> Components: Configuration Admin
> Affects Versions: configadmin-1.9.10
> Reporter: Jürgen Albert
> Assignee: Carsten Ziegeler
> Priority: Major
> Fix For: configadmin-1.9.16
>
>
> As discussed at the OSGi F2F in Berlin. It is often the case, that a
> configuration needs a configuration plugin (like a plugin that sets database
> connection password from a secure store). At the moment, it is hard to
> guarantee that a plugin is known to the ConfigAdmin before a Configuration
> gets applied. Thus 2 things might be usefull:
> # ConfigurationAdmin should propagate what ConfigurationPlugins are known to
> him via a property on its service registration. Suggest would be to have a
> Marker property on a ConfigurationPlugin, Config Admin can pick up. This
> property could be "config.plugin.id". The ConfigAdmin could be
> "config.plugins".
> # Define a system property the ConifgAdmin reads, that name a comma
> separated list of config plugin ids, it waits for before it registers its
> service.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
