[KARAF-5843] Programmatically Created Configs are not persisted in `karaf.etc`

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Not A Problem
• Affects Version/s: 4.1.5
• Component/s: karaf
• Assignee: Jean-Baptiste Onofré
• Reporter: Cetra Free
• Created: 18/Jul/18 01:30
• Updated: 13/Sep/18 19:00
• Resolved: 17/Aug/18 04:52

Description

When using OSGi's ConfigurationAdmin via a blueprint bean, it doesn't save the configuration in the `etc` directory if the file doesn't exist before calling update(props).

Rather it saves it in the file cache.

I.e, if I update a config of `com.example.config` I'd expect that to be persisted in the following location:

etc/com.example.config.cfg

Instead, I see it in this location:

data/cache/bundle8/data/config/com/example/config.config

If the file exists in the location beforehand, this appears to work OK.

Example blueprint:

<reference id="configurationAdmin" interface="org.osgi.service.cm.ConfigurationAdmin"/>
<bean id="persistCheck" class="com.example.PersistCheck" init-method=" init" >
    <property name="configurationAdmin" ref="configurationAdmin" />
</bean>

Example Java Class:

import org.osgi.service.cm.Configuration;
import org.osgi.service.cm.ConfigurationAdmin;

import java.io.IOException;
import java.util.Dictionary;
import java.util.Hashtable;

public class PersistCheck {

    public ConfigurationAdmin getConfigurationAdmin() {
        return configurationAdmin;
    }

    public void setConfigurationAdmin(ConfigurationAdmin configurationAdmin) {
        this.configurationAdmin = configurationAdmin;
    }

    ConfigurationAdmin configurationAdmin;

    public void init() throws IOException {

        Configuration configuration = configurationAdmin.getConfiguration("com.example.config", "?");
        Dictionary<String, Object> props = new Hashtable<>();
        configuration.update(props);

    }

}