That's a very good question :-) A config admin implementation by itself doesn't start out with any configurations. You need something to feed it configurations, at which point it will persist them and feed them to MS, MSF, and ConfigurationListeners and configuration queries as appropriate. You have accurately determined this and written something to feed configurations into config admin from files. From your description your implementation sounds perfectly adequate and correct. IIUC it doesn't deal with factory PIDs however which means MSF won't work.
I think that felix fileinstall does something very similar, see http://felix.apache.org/site/apache-felix-file-install.html although it also will try to install bundles it finds. On the other hand it supports factory PIDs. hope this helps. david jencks On Oct 7, 2013, at 9:16 AM, bokie <[email protected]> wrote: > Hi David, > > My confusion sits more on the part of sending off the config data to the > interested parties (ManagedService or ManagedServiceFactory). > > Some texts that I read seem to convey that the Configuration Admin Services > can also "serve" config data from files within a directory - is this so or > is it mis-interpretation on my part. > > What I've been doing is the following: > - I create configuration files (xml or properties) where the file names > match PID's, I then dump these files in a known directory. > - I create a bundle that scans the known directory, process the files using > Apache Commons Configuration and pass the configuration data with something > like: *configurationAdmin.getConfiguration(pid, null).update(properties)* > where the configurationAdmin is "acquired" using declarative services. > > Thanks and sorry for the confusion > Jorge > > > > > -- > View this message in context: > http://apache-felix.18485.x6.nabble.com/Configuration-Admin-tp5005386p5005388.html > Sent from the Apache Felix - Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
