Hi, On 18.02.2010 22:06, Csakany Robert wrote: > You are absolutely right :) I'm thinking about XML, because there can be > ManagedFactory configuration also, and for this some structure is needed > I'll investigate how to do to be clear - because the ManagedFactory > configurations. (Maybe that style like log4j.properties - the path is > described "." separated). Thanks for the suggestion, I forget this important > rule - minimal dependency :)
Factory configurations are almost exactly the same as regular configurations. The only difference is that they have a service.factoryPid property identifying the factory and the service.pid is generated by Configuration Admin. So I would rather suggest to follow the Felix FileInstall way of defining the configuration files -- in fact using the same format might enable you to possibly reuse existing code. Regards Felix > > Regards, > > Robert > > On Feb 18, 2010, at 9:42 PM, Bertrand Delacretaz wrote: > >> On Thu, Feb 18, 2010 at 9:30 PM, Csakany Robert <[email protected]> wrote: >>> ...I've started analyzing the problem, and I've starting the initconfig >>> bundle for it in Felix project (It will utilize ConfigAdmin service as >>> Justin pointed) . It will check the MANIFEST.MF (Bundle-InitialConfig >>> entry) for a configured folder where the configurations will be stored >>> in XML format.... >> >> Why not properties files instead of XML? >> >> Using XML introduces a dependency on an XML parser...but of course as >> you're implementing it, the choice is yours ;-) >> >> -Bertrand > >
