Hi Gunnar, I will try the strategy of placing the JAR on the system classpath and using the org.osgi.framework.system.packages.extra directive to expose the packages to my bundles.
Thanks, -Mike THIS MESSAGE IS INTENDED FOR THE USE OF THE PERSON TO WHOM IT IS ADDRESSED. IT MAY CONTAIN INFORMATION THAT IS PRIVILEGED, CONFIDENTIAL AND EXEMPT FROM DISCLOSURE UNDER APPLICABLE LAW. If you are not the intended recipient, your use of this message for any purpose is strictly prohibited. If you have received this communication in error, please delete the message and notify the sender so that we may correct our records. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Gunnar Wagenknecht Sent: Friday, September 10, 2010 3:17 AM To: [email protected] Subject: Re: [equinox-dev] OSGi/Equinox and Java SPI Hi Michael, Am 09.09.2010 14:57, schrieb Michael Furtak: > 1) Is the general incompatibility between OSGi/Equinox bundles and SPI a > known issue? In general, this combination is problematic. It doesn't work at all when the consumer side only uses the system class loader. There are workarounds using fragments or buddy class-loading if the consumer side also is an OSGi bundle. > 2) Is there a workaround I can use to get things working? The only workaround for you is to make the library available to the system classloader. You can then make the library packages available to your OSGi bundles using boot delegation. -Gunnar -- Gunnar Wagenknecht [email protected] http://wagenknecht.org/ _______________________________________________ equinox-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/equinox-dev _______________________________________________ equinox-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/equinox-dev
