AnsweredAssumed Answered

Setting a context classloader when calling client code

Question asked by meyerd on Apr 3, 2011
Latest reply on Apr 8, 2011 by meyerd
In ReflectUtil we currently use the custom classloader (ProcessEngineConfiguration.getClassLoader()) for loading JavaDelegate-Classes.

Don't we need to set that ClassLoader as a context-classloader on the current thread when we call the clientcode?

One scenario where it is needed is when we are running in an application server and activiti is deployed as a different application than the application providing the processes and the client code.

Does anyone see a problem arising from setting the custom classloader as context classloader on the current thread (if it is avaliable) ?