The thread context classloader has no specified meaning in OSGi. So
unless you set it to something specific you can not rely on its value.
So I think the observed behaviour is not a bug.
If you want to access the bundle classloader you can access it by
this.getClass().getClassLoader().
Chris
Hello,
I am using Karaf 3.0.3 on JDK 1.7, I noticed a behaviour by Aries Blueprint
which seems a little odd to me. We have created a bundle which gets
initialized/activated using blueprint, within the blueprint.xml we have a
bean with init-method defined to it. I noticed that the classloader used