Got it! Thanks for the explanation Felix. My use case was this, to provide framework extensions which access the private API of the system bundle (which extension bundles can do) then expose services.
This would have worked beautifully. However, temporarily we will have to expose private packages until such a time as those APIs are re-engineered into more modular ones. - Ray On Mon, Oct 28, 2013 at 4:15 AM, Felix Meschberger <[email protected]>wrote: > Hi > > Am 27.10.2013 um 18:53 schrieb Raymond Auge <[email protected]>: > > Sigh... too bad! (but I'm glad it's coming). > > I'm then wondering if DS will scan bundles when extensions attach to them? > i.e. a work around for not having "start-able extensions" would be to use > DS components provided by the extension. > > If DS scanned bundles having been attached (including the system bundle) > it could have worked. > > > DS supports components provided by fragments with two caveats: (1) the > host bundle must support this by setting the Service-Components header such > that component descriptors provided by fragments can be found > (Service-Component headers from fragments are ignored) and (2) only wired > fragments are considered when the host bundle becomes active. > > I fear, this does not work for the system bundle because (a) the system > bundle in general does not have the Service-Components header and (b) the > system bundle only becomes active on framework startup. > > Regards > Felix > > > Ray > > > On Sun, Oct 27, 2013 at 1:47 PM, BJ Hargrave <[email protected]> wrote: > >> Before Core R6 (which is still under development), framework extension >> bundles did not have a standard way of being "activated". A new feature [1] >> in Core R6, will allow framework extension bundles to be activated. >> >> [1] >> https://github.com/osgi/design/blob/master/rfcs/rfc0204/rfc-0204-ExtensionBundleActivators.pdf >> -- >> >> *BJ Hargrave* >> Senior Technical Staff Member, IBM >> OSGi Fellow and CTO of the *OSGi Alliance* <http://www.osgi.org/>* >> **[email protected]* <[email protected]> >> >> office: +1 386 848 1781 >> mobile: +1 386 848 3788 >> >> >> >> >> >> From: Raymond Auge <[email protected]> >> To: OSGi Developer Mail List <[email protected]> >> Date: 2013/10/27 13:24 >> Subject: [osgi-dev] service from extension bundle? >> Sent by: [email protected] >> ------------------------------ >> >> >> >> While I'm sure this is well documented I just can't seem to find it. >> >> Is there any way to trigger the activation of a service provided via an >> extension bundle on the system bundle? >> >> -- >> *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile> >> (@rotty3000) >> Senior Software Architect >> *Liferay, Inc.* <http://www.liferay.com/> (@Liferay) >> _______________________________________________ >> OSGi Developer Mail List >> [email protected] >> https://mail.osgi.org/mailman/listinfo/osgi-dev >> >> >> >> _______________________________________________ >> OSGi Developer Mail List >> [email protected] >> https://mail.osgi.org/mailman/listinfo/osgi-dev >> > > > > -- > *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile> > (@rotty3000) > Senior Software Architect > *Liferay, Inc.* <http://www.liferay.com/> (@Liferay) > > > > > _______________________________________________ > OSGi Developer Mail List > [email protected] > https://mail.osgi.org/mailman/listinfo/osgi-dev > > > > _______________________________________________ > OSGi Developer Mail List > [email protected] > https://mail.osgi.org/mailman/listinfo/osgi-dev > -- *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile> (@rotty3000) Senior Software Architect *Liferay, Inc.* <http://www.liferay.com> (@Liferay)
_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
