"adrian(a)jboss.org" wrote : | I'll fix it properly, but it is slightly complicated in that step (2) isn't the | correct thing to do if the class doesn't match the parent filter. Actually, I think there's an issue with doing that, in that the parent cache could get flushed due to a new deployment in that domain while the child blacklist is not. I need to think about the way this works to make it more efficient. But I don't think the blacklist optimaztion is as important as the caching so I'll fix the use in BaseClassLoaderDomain.loadClass() and do a release of 2.0.6 I'll have to come up with a more optimal solution for 2.0.7 :-) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228600#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...