Hi Stefan,
Stefan Groschupf wrote:
> to realize singletons you have to use a plugin class implementation
> that hosts all resources you want to share within your extension objects.
> Extension objects are not singletons since they are many times used in
> a multithreaded environment. So just mo
Hi all,
some thoughts about the plugin package:
Currently the method Extension.getExtensionInstance returns a new
instance of an extension each time it is called. If an extension is a
singleton, each extension has to implement the singleton pattern.
My suggestion:
Add an instance cache to the Ex
Doug Cutting wrote:
> Stefan Groschupf wrote:
>
>>> I have two more ideas:
>>> 1) create NutchConf as interface (not class)
>>> 2) make it work as plugin
>>
>>
>> I like the idea to make the conf as a singleton and understand the
>> need to be able to integrate nutch.
>> However I would love to d
Hi,
Stefan Groschupf wrote:
[...]
> Any comments, improvement suggestions, more use-cases?
I completely agree with you.
I have two more ideas:
1) create NutchConf as interface (not class)
2) make it work as plugin
1) If NutchConf is an interface, the NutchConf implementation can be
written with
Hi Andrzej,
Gal Nitzan wrote:
>> It seems that Trunk is now broken...
>>
DmozParser seems to be broken, too. It's package declaration is still
org.apache.nutch.crawl instead of org.apache.nutch.tools.
TJ
Hi Andrzej,
Gal Nitzan wrote:
> It seems that Trunk is now broken...
>
DmozParser seems to be broken, too. It's package declaration is still
org.apache.nutch.crawl instead of org.apache.nutch.tools.
TJ
Hi Andrzej,
Gal Nitzan wrote:
>> It seems that Trunk is now broken...
>>
DmozParser seems to be broken, too. It's package declaration is still
org.apache.nutch.crawl instead of org.apache.nutch.tools.
TJ
