I've hit a problem with ContextClassLoaderServiceDiscoverer when
multiple Nodes are started with different Thread Context ClassLoaders
in that ContextClassLoaderServiceDiscoverer always returns its cached
classloader which is from the TCCL of the first Node that was started.
I've changed this in r899589 so getContextClassLoader just returns the
current TCCL which gets my test passing, but the
ContextClassLoaderServiceDiscoverer is still using the cached one in
other places, is there any reason this couldn't just be using the
current TCCL everywhere?

   ...ant

Reply via email to