I suspect you know this but NoClassDefError means that the classloader
resolved the class and then it started to try and get hold of the byte
code. When it tried to load the byte code it was blocked from loading
it by the OSGi bundle classloader policy. When I have seen this in the
past, the manifest is missing an import, but sometimes its not the
import mentioned in the NoClassDefError but that something that needs
to be there to load the class. (interfaces etc).
I probably got some of that wrong, not being internal to any OSGi
container.
Although this looks like an internal class to the bundle the
findClassOrResourceByDelegation might be significant.
Ian
On 26 Nov 2009, at 09:02, Christophe Lombart wrote:
Hi all,
I would like to work on the issue SLING-1190 (Upgrade Jackrabbit
dependency
to 1.6). I don't understand why I got the exception (see more in [1]).
I don't see a big difference between J 1.5 & J 1.6 in this area. So,
I need
help :-)
thanks,
Christophe
[1] https://issues.apache.org/jira/browse/SLING-1190
