[ http://issues.apache.org/jira/browse/NUTCH-210?page=all ]
Chris A. Mattmann updated NUTCH-210:
------------------------------------
Attachment: NUTCH-210.Mattmann.patch.txt
Initial NUTCH-210 patch. Uses an XSL stylesheet to read searcher., plugin.,
extension.clustering and extension.ontology configuratin parameters out of
nutch-default.xml and convert them into a deployable context.xml file
(nutch.xml), which is written to the $NUTCH_HOME/build directory when a war
file is created. Updated JSP pages to override Nutch configuration parameters
with parameters specified in the nutch.xml context file. Now, dynamic
properties such as searcher.dir and so forth can be modified without having to
build a new Nutch war file. Please give the patch a look.
> Context.xml file for Nutch web application
> ------------------------------------------
>
> Key: NUTCH-210
> URL: http://issues.apache.org/jira/browse/NUTCH-210
> Project: Nutch
> Type: Improvement
> Components: web gui
> Versions: 0.7.1, 0.7, 0.6, 0.7.2-dev, 0.8-dev
> Environment: iMAC G5 2.3 Ghz, Mac OS X Tiger (10.4.3), 1.5 GB RAM, although
> improvement is independent of environment
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Priority: Minor
> Fix For: 0.7.2-dev, 0.8-dev, 0.7.1
> Attachments: NUTCH-210.Mattmann.patch.txt
>
> Currently the nutch web gui references a few parameters that are highly
> dynamic, e.g., searcher.dir. These dynamic properties are read from the
> configuration files, such as nutch-default.xml. One problem I'm noticing
> however is that in order to change the parameter in the built webapp (the WAR
> file), I am required to change the parameter first in the checked out Nutch
> source tree, rebuild the webapp, then redploy. Or, if I'm feeling really
> gutsty, I can go poke around in the unpackaged WAR file if the servlet
> container exposes it to me, and try and modify the nutch-default.xml file
> that way. However, I think that it would be really nice (and highly useful
> for that matter) to factor out some of the more dynamic parameters of the web
> application into a separate deliverable Context.xml file that would accompany
> the webapp. The Context.xml file would be deployed in the webapps directory,
> as oppossed to the WAR file itself, and the parameters could be updated
> there, and changed as many times as necessary, without rebuilding the WAR
> file.
> Of course this will involve making minor modifications in the web GUI to
> where some of the dynamic parameters are read from (i.e., make it read them
> from the Context.xml file (using application.getParameter most likely). Right
> now the only one I can think of is searcher.dir, but I'm sure that there are
> others (in particular the searcher.dir one is the most annoying for me).
> The timeframe on this patch will be within the next month.
> Thanks,
> Chris
--
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
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
_______________________________________________
Nutch-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nutch-developers
