> Right, I see this now. But one question: Can the proxyBundle be > *any* other bundle or does it have to be a this static dummy bundle? > i.e. could it be (for example) one of the ECF core bundles? >
Yes with one proviso, that bundle cannot import any package containing a service you want to proxy. If it does, then the special extender "privilege" is lost. So it seems that is a risk to be considered. Also, the life cycle of the proxied services is tied to that bundle. Which is another reason to use a "dummy" bundle for that purpose. You can lifecycle manage the ECF core bundle without upsetting the proxied services (of course that may not be possible if the bundle being stopped is critical to the function of the proxied services). So if you have some core ECF bundle which just holds your API (for example just exports API packages), then you could use that bundle as the "host" of the proxied services. -- BJ Hargrave Senior Technical Staff Member, IBM OSGi Fellow and CTO of the OSGi Alliance [email protected] office: +1 386 848 1781 mobile: +1 386 848 3788
_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
