AbstractInvoker and thread context classloader

[igorfie]

I am not sure if this is the right place to raise this issue, but shouldn't AbstractInvoker use Thread.currentThread().getContextClassLoader() to initialize classbyteloader? Currently it uses this.getClass().getClassLoader() which assumes that jboss-remoting.jar and my classes are loaded by the same classloader, which is not always possible. In my case, jboss-remoting.jar belongs to one Eclipse plugin and EJB3 client interfaces to another and I get ClassNotFoundException whenever I try to call an EJB.

[starksm64]

The dynamic class loading in the current remoting framework is just broken. It cannot handle loading classes outside of its codebase. Just using the thread context class loader is not adequate as this is not typically set correctly until the invocation has been dispatched to the application context. The class loading in the remoting framework is being overhauled along with the framework itself to be consistent with the rest of the microkernel in jboss 5.

[tom.elrod]

Think is refering to org.jboss.remoting.AbstractInvoker. Will fix. Thanks.

-Tom