You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by "Stefan Groschupf (JIRA)" <ji...@apache.org> on 2006/01/10 13:53:20 UTC

[jira] Updated: (NUTCH-169) remove static NutchConf

     [ http://issues.apache.org/jira/browse/NUTCH-169?page=all ]

Stefan Groschupf updated NUTCH-169:
-----------------------------------

    Attachment: nutchConf.patch

The patch was created by Marko Bauhardt with some  help from me, so full credits to Marko! 
It remove any access of nutchConf via the static method 'get'. Therefore some API was changed to pass a instance of the NutchConf down the call stack to be available in all required objects. 
For performance reasons the PluginRepository is now cached in the nutchConf. The Repository will not be serialized and re-instantiated as soon it is requested.  
The complete test suite is passing with this patch, only Jerome's new HTML protocol need to port to the new NutchConf API also. 
Jerome mentioned that he will do this. (Thanks)  
I would be great if we can bring this patch somehow soon to the svn, since this is just the first step to a nutch gui.
 

> remove static NutchConf
> -----------------------
>
>          Key: NUTCH-169
>          URL: http://issues.apache.org/jira/browse/NUTCH-169
>      Project: Nutch
>         Type: Improvement
>     Reporter: Stefan Groschupf
>     Priority: Critical
>      Fix For: 0.8-dev
>  Attachments: nutchConf.patch
>
> Removing the static NutchConf.get is required for a set of improvements and new features.
> + it allows a better integration of nutch in j2ee or other systems.
> + it allows the management of nutch from a web based gui (a kind of nutch appliance) which will improve the usability and also increase the user acceptance of nutch
> + it allows to change configuration properties until runtime
> + it allows to implement NutchConf as a abstract class or interface to provide other configuration value sources than xml files. (community request)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira