[nanocontainer-scm] [jira] Created: (NANO-134) Classloader problem when a nanocontainer with the xml scripting builder runs in a eclipse rcp client

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

         Key: NANO-134
         URL: http://jira.codehaus.org/browse/NANO-134
     Project: NanoContainer
        Type: Bug
  Components: eclipse  
 Environment: Eclipse RCP 3.0, Nanocontainer snapshot (12-april-2005)
    Reporter: Reto Breitenmoser
    Priority: Minor
 Attachments: XMLContainerBuilder.java

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

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira