[jboss-dev-forums] [Design the new POJO MicroContainer] - Re: Remaing classLoader changes

[scott.stark@jboss.org]

One difference in behavior I'm seeing that we don't appear to have control over is duplicate resource ordering. The org.jboss.test.deployers.vfs.classloader.test.FilteredExportUnitTestCase.testEar1 test I just added shows a users.properties resource being loaded from the testear1/lib/jar1.jar rather than the testear1.ear/ejb1.jar as is the case for the ULR. In the ULR we give preference to exact matches on latter ordered classes loaders. If I turn off the import all flag, the ejb1.jar resource is found, but this is too restrictive a policy. We need a import-all-exact-match-first type of behavior it seems.


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

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