[ARIES-1841] Cleanup on cm-properties

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: blueprint-core-1.9.0, blueprint-core-1.8.3
• Fix Version/s: blueprint-core-1.8.4, blueprint-core-1.9.1
• Component/s: Blueprint
• Assignee: Jean-Baptiste Onofré
• Reporter: Jean-Baptiste Onofré
• Created: 03/Oct/18 13:15
• Updated: 07/Nov/18 17:43

Description

If a blueprint bundle use CM like:

<cm-properties persistent-id="persistentId" id="my.config" xmlns="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.2.0"/>

if the configuration is created by another bundle (directly using ConfigurationAdmin) like:

        Configuration configuration = configurationAdmin.getConfiguration(CONFIG_PID, null);
        Dictionary<String, Object> dictionary = Optional.ofNullable(configuration.getProperties()).orElse(new Hashtable());
        for (Map.Entry entry : properties.entrySet()) {
            dictionary.put(entry.getKey().toString(), entry.getValue());
        }
       configuration.update(dictionary);

then, it's possible to have a race condition where the blueprint container thread starts whereas the config update is not complete (two different threads).

Blueprint CM should have an option to wait an updated config. For instance, it could check _felix_.cm.newConfiguration property.