In Fuse 6.2, Thread.currentThread().getContextClassLoader() returns a different classloader than in Fuse 6.1

-There is some difference in classloaders used in 6.1 and 6.2. This is also reproducible locally(attached is the test-case).

• A test bundle activator code-snippet

   @Override
   public void start(BundleContext arg0) throws Exception {
           
       ClassLoader cl1 = Thread.currentThread().getContextClassLoader();
       ClassLoader cl2 = this.getClass().getClassLoader();
       logger.info("cl1: "+cl1+ " ; cl2: "+cl2);
           
   }
  

• Behaviour of this snippet in Fuse 6.1 and 6.2 is different.
• In Fuse 6.1, It prints

   14:04:42,119 | INFO  | l Console Thread | ActivateTest                     |
   256 - camel-bundleactivator-example - 1.0.0 | cl1:
   camel-bundleactivator-example [256] ; cl2: camel-bundleactivator-example [256]
  

• Observation: cl1 and cl2 both are same.
• In Fuse 6.2, It prints

   2015-07-15 14:05:40,017 | INFO  | l Console Thread | ActivateTest
   | 280 - camel-bundleactivator-example - 1.0.0 | cl1:
   sun.misc.Launcher$AppClassLoader@92524b0 ; cl2:
   camel-bundleactivator-example [280]
   

• Observation: cl1 and cl2 are different. cl1 returns
  "sun.misc.Launcher$AppClassLoader@92524b0".