Classloader problem when a nanocontainer with the xml scripting builder runs in a eclipse rcp client

If the nanocontainer with the XMLContainerBuilder runs in the eclipse RCP environment, it gives classloader problems. In the method createComponentInstanceFactory(String factoryClass) a new DefaultNanoContainer is instantiated with the empty constructor. The DefaultNanoContainer tries to load the xxxComponentInstanceFactory first from an url and then it tries from the parent classloader. But in the parent classloader are only three eclipse classes. If the DefaultNanoContainer is instantiated with the classloader from the parent container, then it is configurable.

Please verify if this is correct. Maybe there was reason why the DefaultNanoContainer in the createComponentInstanceFactory method was instantiated without the classloader.

In the attachement is the XMLContainerBuilder class with the patch.

Thanks
Reto