[jboss-dev-forums] [Design the new POJO MicroContainer] - Reflect BeanInfo cache change breaks Kernel

[alesj]

Looks like our change
 - http://www.jboss.com/index.html?module=bb&op=viewtopic&t=145938&start=20
to Reflect's BeanInfo caching is the cause of this:
 - http://lists.jboss.org/pipermail/jboss-development/2008-November/013128.html

Since when I change this in Kernel, to use 2.0.1.GA,
DeploymentClassLoaderTestCase test is failing:

  | testDeploymentClassLoader(org.jboss.test.kernel.deployment.test.DeploymentClassLoaderTestCase)  Time elapsed: 0.031 sec  <<< FAILURE!
  | junit.framework.AssertionFailedError: expected:<org.jboss.test.classloading.vfs.VFSClassLoader at 1aaf194> but was:<org.jboss.test.classloading.vfs.VFSClassLoader at e3990b>
  | 	at junit.framework.Assert.fail(Assert.java:47)
  | 	at junit.framework.Assert.failNotEquals(Assert.java:277)
  | 	at junit.framework.Assert.assertEquals(Assert.java:64)
  | 	at junit.framework.Assert.assertEquals(Assert.java:71)
  | 	at org.jboss.test.kernel.deployment.test.DeploymentClassLoaderTestCase.testDeploymentClassLoader(DeploymentClassLoaderTestCase.java:59)
  | 

Looks like ClassInfo is not 'immune' to different classloaders.
Should I put back CL as additional key?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4192069#4192069

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4192069