On Wed, Jul 07, 2004 at 12:13:46AM +0200, Stefan Groschupf wrote: > 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? > > >
Hi, Stefan, > > 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. For example, in ./nutch/src/plugin/parse-text/src/java/net/nutch/parse/text/TextParser.java, I would like to be able to retrieve all the attributes in ./nutch/src/plugin/parse-text/plugin.xml, especially those in <implementation ..> Or is there already a way that I have overlooked? John ------------------------------------------------------- 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
