These companion code jars are not really intended for runtime use. They are intended to compile time use. It is expected that at runtime, some other jar, such as the implementation jar, would export the related package.
The companion code jars are companions to a specification and thus contain the API for the complete content of the specification. You are free to repackage the API as you see fit. -- BJ Hargrave Senior Technical Staff Member, IBM OSGi Fellow and CTO of the OSGi Alliance hargr...@us.ibm.com office: +1 386 848 1781 mobile: +1 386 848 3788 From: Balázs Zsoldos <balazs.zsol...@everit.biz> To: osgi-dev@mail.osgi.org, Date: 2012/05/08 06:26 Subject: [osgi-dev] OSGI cmpn and enterprise jars Sent by: osgi-dev-boun...@mail.osgi.org Hi, I would have a couple of question about the cmpn and enterprise jars. Why are there two jars with almost the same content. I need for example the jdbc DataSourceFactory interface so I use the enterprise jar. However if I need something from the cmpn jar and I also use Blueprint I will meet the problem that there are two jars with the same package will exist. Now if: osgi enterprise starts blueprint container starts compendium starts a bundle that uses the BlueprintListener interface to catch Blueprint events starts then the bundle will not catch the events as the bundle may use different interface than the blueprint container. Is there any practical reason for this or is there a jar that merges the two? Regards, Balazs Zsoldos Software Architect Mobile: +36-70/594-92-34 Everit Kft. https://www.everit.biz _______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
