We are considering to use Configuration Admin Service as a primary API for configuring components in our OSGi-based application. It would be nice if we could reuse some existing implementation so I’m trying to investigate and evaluate the most popular ones. I know there is:
- Apache Felix Config Admin (org.apache.felix.cm)
- Equinox Config Admin (org.eclipse.equinox.cm)
Are there any other implementations to be considered?
Also I was not able to find any good documentation for these implementations. I would be mainly interested in the implementation-specific details. For example I was wondering how different implementations persist the configuration data (e.g. multiple property files? XML file? multiple XML files? database?, …).
The three public implementations I know of are
Equinox’s implementation of the
ConfigurationAdminservice appears not to support fine control over the persistence policy, as Felix’s does, and the Knopflerfish implementation looks (I’ve only read the source briefly) similar to Equinox’s.The Felix one appears to be the most recently updated and the most reliable.
At present these are the only ones I can find; at dm Server we made the decision to use Felix’s bundle, and this is now obtainable from the SpringSource Enterprise Bundle Repository, where you can quick-search for
Apache FelixorConfigAdmin.