I have a non OSGI library file which has an API(method) which takes className as input & it tries to load the class using Class.forName.
This works fine in java. But i have created a bundle from the jar using maven plugin. i.e, I have added OSGI nature to it.
I have say 3 projects
1. My OSGI bundle - "BundleA".
2. NON osgi Library project "LibB". - converted to OSGI using BND tool or Maven
2. NON osgi Library project "LibC". - converted to OSGI using BND tool or Maven
LibsC - is the one explained above having the code class.forName. - 3rd party library
LibB - like intermediate library
BundleA - Exports a package say com.company.test
BudleA calls a service from LibB which inturn calls the method having loadClass(className) which takes class name from BundleA which is exported from bundle.
I have added <DynamicImport-Package>*</DynamicImport-Package> in manifest of LibC
Irrespective of whether or not it turns out to be possible, it's probably not a good idea to do your own dynamic class loading within a dynamic class loading environment like OSGi.
The thing is that OSGi has a highly restrictive idea of what a classpath is; for a given bundle it's essentially the classes within that bundle, and everything that gets imported - nothing else. So the class you're trying to load would need to be part of the bundle or part of one of its imports.
But there are likely better solutions to whatever the underlying problem is that you're trying to solve.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com