-
1. Re: Issues with BluePrint and ServiceTracker
thomas.diesler Sep 24, 2012 3:27 AM (in response to charlie7)This should work in theory. What does the debug log say?
-
2. Re: Issues with BluePrint and ServiceTracker
charlie7 Sep 24, 2012 12:21 PM (in response to thomas.diesler)Further checking I found that having the startlevel="2" was not starting up aries , blueprint etc
After making them as follows
<capability name="org.apache.aries:org.apache.aries.util:0.4" />
<capability name="org.apache.aries.proxy:org.apache.aries.proxy:0.4" />
<capability name="org.apache.aries.blueprint:org.apache.aries.blueprint:0.4" />
starts all of them . I say that w.r.t the checkmark in the OSGI section of the admin console
After this I am able to access the services through the ServiceTracker
Thanks
-
3. Re: Issues with BluePrint and ServiceTracker
thomas.diesler Sep 24, 2012 9:12 PM (in response to charlie7)Having those bundles at startlevel=2 should also work. Did you tell the framework to go up to that level?
<!-- Specifies the beginning start level of the framework -->
<property name="org.osgi.framework.startlevel.beginning">2</property>