Re: Using a service tracker on ConfigurationAdmin from outside the framework

Hmm. This indicates that previously the cm export was satisfied by another bundle. Which of course it was because the Felix Config Admin implementation exports that package (in addition to importing it). I am a little uncomfortable relying on this. I believe it would be legal for the framework

Re: Using a service tracker on ConfigurationAdmin from outside the framework

This should work, but without a code sample it’s impossible to say what might be going wrong. The usual pattern would be: 1. Init and start the framework 2. Install the bundles, including configadmin 3. Create and open your tracker 4. Start the bundles 5. Enter framework.waitForStop(), where

Using a service tracker on ConfigurationAdmin from outside the framework

My current task is to set up a Felix framework behind an API. To get actual work done, there are some interfaces in packages on the system bundle that are published by bundles of mine, and then the code 'outside' the framework obtains them. For the main service I created, this all works find with

Re: Using a service tracker on ConfigurationAdmin from outside the framework

As usual, the answer occurred to me moments after I pressed 'send'. I neglected to specify a version for org.osgi.service.cm when adding it to the system bundle export list. On Sun, Sep 18, 2016 at 3:18 PM, Neil Bartlett wrote: > This should work, but without a code sample

Re: Using a service tracker on ConfigurationAdmin from outside the framework

On Sun, Sep 18, 2016 at 3:53 PM, Neil Bartlett wrote: > Hmm. This indicates that previously the cm export was satisfied by another > bundle. Which of course it was because the Felix Config Admin implementation > exports that package (in addition to importing it). Yes,