Description
An updated OSGi Config Admin Service implementation based on our JNDI backing store will soon be available for code review and experimental testing. This updated implementation of the OSGi Configuration Admin Service will use the jndi backing store to persist configuration admin data for it's clients based on custom schemas that are associated with each client type.
Several ApacheDS OSGi modules (like the protocol providers) will support dynamic configuration administration through the OSGi Configuration Admin service. Each of these OSGi Configuration Admin 'clients' will require a custom schema and thus an unique OID assignment.
To avoid OID collisions request that a branch of the the assigned ApacheDS OID tree be designated as the OSGi branch for OSGi schema OID assignments of required ApacheDS OSGi modules.