File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Other Application Frameworks and the fly likes OSGI class loading Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Frameworks » Other Application Frameworks
Bookmark "OSGI class loading" Watch "OSGI class loading" New topic

OSGI class loading

sandeep kamath

Joined: Aug 21, 2013
Posts: 1
Hi All,

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

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

I am getting classNotFoundException.
Please help
Ulf Dittmer

Joined: Mar 22, 2005
Posts: 42965
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 agree. Here's the link:
subject: OSGI class loading
It's not a secret anymore!