Question

I’d like to create a Configuration object in OSGi, but one that won’t be persisted, so it won’t be there when the framework is restarted. Similar to START_TRANSIENT for bundles.

Some background: I’ve got an OSGi (Felix) based client side application, deployed over OBR. The configuration object I’m talking about effectively boots the application. That works fine, but sometimes the content has changed while the context was stopped. In that case, it boots the application as OSGi revives all bundles and adds all configuration options. Then I inject the correct configuration, the application stops and then restarts again.

So it does actually work, but the app starts twice, and I can’t get access to the framework before it reconstructs its old state.

Any ideas?

Answer 1

As BJ said there is no standard support for this in the Configuration Admin spec.

However the Felix implementation supports two features which may help you. First, you can set the felix.cm.dir property which configures where the configadmin saves its internal state (which by default will be somewhere under the Framework storage directory). You could set this to a location that you control and then simply wipe it every time you start OSGi (you could also wipe out the entire OSGi Framework storage directory on every start… some people do this but it has wider consequences that what you asked for).

Second, if you need a bit more control, Felix ConfigAdmin supports customising its persistence with a PersistenceManager service. You could probably implement this and return empty/doesn’t-exist for the particular pids that you want to control.