John,
[EMAIL PROTECTED] wrote:Currently, the definition of one external parser requires
synchronized change of both file ./nutch/build/plugins/parse-ext/command
and ./nutch/build/plugins/parse-ext/plugin.xml. Ideally
it'd better be handled solely by file plugin.xml. However that would
require attributes in plugin.xml be passed to ExtParser.java, and
I could not figure out a proper way to do it with current plugin system.
Stephan and Doug: any suggestion?
Yes, I agree it would be better if a plugin implementation could access the attributes easily from plugin.xml. Perhaps we should make ParserFactory.getExtension() public, then you can call getAttribute() on the returned Extension. Would that work?
Sorry I'm not sure if I understand your right..
You can lookup all extensions to a extension point in the plugin repository and iterate over the extensions where you can get attributes.
I think to remember that with the snmp patch comes some changes of the plugin system that make such thing more easier.
How ever I need to re commit the patch again since the plugin system has some major bugs that need to be fixed.
This bugs are not critical for nutch today.
I plan to add some more nice functionality to the plugin system but I will write another mail about this issues.
Stefan
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Nutch-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nutch-developers
