[jboss-dev-forums] [JBoss Microcontainer Development] - Re: Testing Deployers with new Reflect + ClassPool

[flavia.rainone@jboss.com]

"alesj" wrote : "flavia.rainone at jboss.com" wrote : that should return a class loaded by a BaseClassLoader, are returning a class loaded by the AppClassLoader.
  | This sounds like the issue we had before -- classes "leaking" into system cl,
  | where we should really only allow java.* packages through.
The point is that the failures I mentioned are being seen on sanity test cases, i.e., with ClassLoaders, no ClassPool involved.

"alesj" wrote : What's the "L loader" in TestScenario.cannotLoadClass(L loader, String className)?
  | Could be by-passing some rules?
The L loader is just a generics abstraction for ClassLoaders and ClassPools, which allow me to write a test without being concerned whether it is going to be run against a ClassLoader or a ClassPool. The same test code is run with ClassLoaders (SanityTestCase) and with ClassPools (ClassPoolTestCase), thus enforcing that both behave the same way.

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

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