&quot;adrian(a)jboss.org&quot; wrote : | 2) The way the IIOP WebCL processing is done now is incorrect in my opinion. | ... | 3) The way the classloaders currently work is that they first check | for the class resource existing. | The simplest way to do this (similar to how it works now) is pretty ugly. i.e. Something like: | public Class<?> loadClass(...) | { | Class<?> result = current classloading code | if (result == null) | result = runClassNotFoundHandlers(this, ...); | if (result == null) | throw ClassNotFoundException(...); | return result; | } | It's ugly in that you've got to allow the ClassNotFoundHandler to say, I'm defining this class against a different classloader so don't invoke defineClass() yourself. The protocol/api that lets it do that, would potentially be a major security hole, it would certainly be open to abuse. :-) The alternative is a lot more complicated since the ClassNotFoundHandler would probably have to take part in the class search and caching algorithms (general solution). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157080#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...