With the change to using a ComponentManager and URIs for components internally, I think we need to decouple ClassLoaders from CompositeComponent as well.

I'm going to add a separate ClassLoaderRegistry to the runtime domain to do this, something like:
interface ClassLoaderRegistry {
   void register(URI id, ClassLoader classLoader);
   ClassLoader get(URI id);
   void unregister(URI id);
}

The actual classloader implementations will generally be MultiParentClassLoader's or CompositeClassLoader's but I don't think we need to restrict to that.
--
Jeremy


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to