You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@nutch.apache.org by "Lewis John McGibbney (JIRA)" <ji...@apache.org> on 2013/01/12 21:14:12 UTC

[jira] [Updated] (NUTCH-589) Hierarchical Classloaders

     [ https://issues.apache.org/jira/browse/NUTCH-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lewis John McGibbney updated NUTCH-589:
---------------------------------------

    Fix Version/s: 1.7
    
> Hierarchical Classloaders
> -------------------------
>
>                 Key: NUTCH-589
>                 URL: https://issues.apache.org/jira/browse/NUTCH-589
>             Project: Nutch
>          Issue Type: Improvement
>    Affects Versions: 0.9.0
>            Reporter: Ryan Levering
>            Priority: Minor
>             Fix For: 1.7
>
>
> Currently the Nutch plugin classloader flattens all the jars from a plugins' dependencies and instantiates a new classloader for each plugin.  I think it would be better to create a hierarchical classloader chain.  Currently plugins can't pass objects from a common plugin to one another because the objects are created using different classloaders.  Nutch currently avoids this by only using interfaces from a common classloader to pass objects between plugins, but I can't see the harm in improving the plugin classloader.  It would require a change to PluginDescription and PluginClassLoader in order to override ClassLoader to maintain the export filter functionality that currently exists.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira