[ https://issues.apache.org/jira/browse/GERONIMO-4470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12656850#action_12656850 ]
David Jencks commented on GERONIMO-4470: ---------------------------------------- I don't see why you think this is a problem. We aren't overriding a definition from a parent classloader, right? With typical use of filters org.foo.package.name. it will be hard to make it so org.foo.package.name.ParentClass is correctly loaded from the parent but a org.foo.package.name.subpackage.ChildClassOnlyInLocalClassloader can be loaded at all. Is this causing any actual problems? > non-overridable filters working properly > ---------------------------------------- > > Key: GERONIMO-4470 > URL: https://issues.apache.org/jira/browse/GERONIMO-4470 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Affects Versions: 2.0.4, 2.1.4, 2.2 > Reporter: Kevan Miller > Fix For: 2.2 > > > If we're unable to load a non-overridable class from a parent classloader and > inverse classloading is configured, looks like we'll try to load the class > from the local ClassLoader. I don't think this is correct. If we're unable to > load from a parent classloader, should always return a > ClassNotFoundException... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.