I am running into an issue where a ManagedService that I register from one of my bundles is not being tracked by the config admin service.
I have other managed services that are being configured just fine, and I traced down the difference to what seems to be a scope issue: the problem bundle is declared in a plan, and it seems that that makes it non-accessible by the config admin service.
Upon registration of the ManagedService the framework goes on to filter the listeners that should be notified, and I end up in the isPotentiallyVisible call below which returns false; in the end no listener is notified of the registration of my ManagedService.
Is it the case that a plan bundle is not visible from the global scope? What is the proper way to resolve this?
Solved this by making my plan non scoped.
It seems like any OSGI service that works on a publish/subscribe model like the Config Admin service does, by monitoring registrations of of a given service class, will be subject to the same issue.
Quite obvious once you have the whole picture, but the symptoms are by no means easy to interpret...
I am bumping into the same issue. When a plan is scoped the Managed Service and Managed Service Factories never get notified of config changes by the Configuration Admin service.
Scoping of plans is a very attractive feature - indeed I am counting on this to avoid service conflicts between my plans. Am I missing something? Is there a way To get the Configuration Admin to work with scoped plans? I am using VTS 3.6.1.