Hi Tim Yes, the spec does not foresee such a thing. And under normal operating conditions such a thing is not needed.
In the Felix CAS implementation the configurations are -- by default and in the absence of PersistenceManager services -- stored in a folder defined by the felix.cm.dir framework property. So you may define this property to be some specific folder, which you make sure does not exist before launching the framework. Hope this helps. Regards Felix Am 03.06.2013 um 17:54 schrieb Tim Diekmann: > Hi, > > Using the current spec, what would be the best way to implement the purging > of configuration data prior to regular operations? > I want all configurations to be removed, before CAS starts notifying MS and > MSF to basically start with a clean environment under certain conditions. > > The problem I am facing right now with Felix CAS 1.4 is the asynchronous > nature of the notifications. Upon startup, CAS notifies all MS and MSF with > the previously persisted config only to be told then by my code to purge them > all. Depending on the timing on startup I sometimes see it work as intended > and sometimes the purging comes after the new creation of the configurations > leaving me without any. > > The only (ugly) solution I can think of working with Felix ConfigAdmin is to > wait for the registration of the PersistenceManager (happens before > ConfigAdmin registration) and telling it to delete all known configurations. > That way, CAS starts with nothing and can then be initialized later with the > fresh config information. > > Felix, do you have a better idea? > > Thanks, > > Tim. > > _______________________________________________ > OSGi Developer Mail List > [email protected] > https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
