Yes this is right. The OSGi bundles have access (potentially) to all framework extra packages and to all packages exported by other bundles, but the framework packages only have access to other framework packages. They are unable to reach into bundles.
However, you can solve this by using the OSGi service registry. The framework packages do have access to that (as long as they can access the BundleContext of the system bundle). So you can have one of the bundles register an OSGi service and the framework can access this service. This is called the whiteboard pattern and used a lot in OSGi. -Stijn -----Original Message----- From: Marco [mailto:[email protected]] Sent: zondag 8 december 2013 18:58 To: [email protected] Subject: non-OSGi lib importing OSGi packages Hello everyone, I would like to ask you this simple question. Let's suppose I have some non-OSGi library imported through system packages extra into the framework. I know that Felix expose the packages to all bundles in the OSGi environment. Now let's suppose one of the libraries wants to use a logger, and I alredy have an OSGi bundle that implements the logger service (e.g. pax logging). Can the library use pax logging, or is necessary to add another non-OSGi library for the logging? In other words (and that's my opinion but I want to be sure), I think that non-OSGi libraries have no access to the OSGi environment, and I can only use them importing some packages through the system.extra or by boot delegation. If that is the case, what I'm supposed to do in order to accomplish the logging task in the proper way? Thank you, Marco -- View this message in context: http://apache-felix.18485.x6.nabble.com/non-OSGi-lib-importing-OSGi-packages-tp5006370.html Sent from the Apache Felix - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
