[ http://issues.apache.org/jira/browse/NUTCH-169?page=comments#action_12362396 ]
Jerome Charron commented on NUTCH-169: -------------------------------------- Notes: 1. The more I look to this solution, the more I think the major problem will be to ensure the propagation of a changed conf to all the impacted classes. 2. Does all properties should be dynamic? > 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.Fetcher.060111.patch, NutchConf.Http.060111.patch, > NutchConf.RegexURLFilter.060111.patch, 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
