Neil, Running that command shows that the correct package is being imported and resolved to the correct bundle.
I should probably also mention that both the class that is being instantiated as well as the class from which it is derived are compiled from Clojure code. This /shouldn't/ matter as there are .class files for both of these classes that are normal Java byte code. But one of the bundles that I'm using is a Clojure OSGi bundle. Clojure is problematic in OSGi as it has its own classloader but this bundle (not created by me) /should/ handle this correctly, but I don't know for sure. Tim On 08/18/2014 05:29 PM, Neil Bartlett wrote: > Does the “problem bundle” import the package? You can check this with the > following command: > > inspect req osgi.wiring.package <bundle-id> > > > Regards, > Neil > > > On 18 August 2014 at 22:09:17, Tim McIver ([email protected]) wrote: > > Hello, > > I'm getting a NoClassDefFoundError when trying to start a bundle that > resolves without error. This happens when trying to instantiate a class > (in the bundle activator) whose .class file resides in the bundle > itself. But the class being instantiated is derived from a class found > in another bundle, already resolved and started. To confirm that I've > got things wired up in the way that I think I do, I ran the following > command at the Felix console: > > g! which <problem-bundle-id> > <fully-qualified-name-of-class-that-gives-noclassdeffounderror> > > > and the response is good (I think): > > Loaded from: <com.example.impl> [50] > > > where 50 is indeed the ID of the bundle where I'm exporting package > com.example.impl. Any idea what could be causing this? > > Thanks, > Tim > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
