I know we have plans to add this in the new VFS ClassLoader
and it is already sort of present in the Tomcat classloader.
But, it would be useful if we could filter out certain parts from the classloading.
e.g. a common problem is people breaking their jndi config by having a jndi.properties
in their deployments.
Yes, I want a completely configurable class loading context that can specify classes and resources to exclude. I wanted to have the features of the osgi and new java package thing if possible and then look at what could be brought back to 4.0.