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.