The following seems to work...
When my PerstenceManager becomes active it can push all the
configurations known to it to the ConfigurationAdmin service, like
this:
ConfigurationAdmin caService = ... from service registry ...
for(String pid : myConfigurations) {
Configuration config = osgiConfigAdminService.getConfiguration(pid, null);
config.update(getDictForConfiguration(pid));
}
Is this the recommended approach?
Cheers,
David
On 25 May 2012 15:48, David Bosschaert <[email protected]> wrote:
> Hi all,
>
> I have a custom persistence manager used with Felix ConfigAdmin. When
> I activate this persistence manager additional configuration objects
> may become available to configadmin (because the persistence manager
> has stored these).
>
> When I'm registering my PersistenceManager as follows:
> context.registerService(PersistenceManager.class.getName(),
> myPersistenceManager, props);
> I can see that it's being used for subsequent ConfigAdmin operations
> (e.g. to store configuration that is added), but how can I tell the
> system to consult the PersistenceManager to discover any additional
> configuration that it may provide?
> I would have expected that the simple registration of a new
> PersistenceManager service would be enough of a cue to the Config
> Admin impl to check it for additional configs?
>
> Thanks,
>
> David
>
> BTW I'm using ConfigAdmin 1.2.8
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
