Mailing-List: contact stanbol-commits-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: stanbol-dev@incubator.apache.org
Date: Wed, 16 Mar 2011 10:04:30 +0000 (UTC)
From: "Rupert Westenthaler (JIRA)" <jira@apache.org>
To: stanbol-commits@incubator.apache.org
Message-ID: 
 <1166596885.6193.1300269870007.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <325141869.4409.1300214430046.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Issue Comment Edited: (STANBOL-115) Provide Default
 Configuration and Automatic Initialization for the Entityhub in the Stanbol
 Enhancer Full Launcher
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/STANBOL-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007396#comment-13007396 ] 

Rupert Westenthaler edited comment on STANBOL-115 at 3/16/11 10:03 AM:
-----------------------------------------------------------------------

I would rather do that within STANBOL-92, because this issue is about packing also a local index that can be used in combination with the ReferencedSiteEntityTaggingEnhancementEngine. Than such an integration test can run offline and there would be no danger to make Hudson unhappy if the SPARQL service at dbpedia.org is unavailable.

In addition as soon as STANBOL-92 is resolved we can also
 - remove the Autotagger
 - replace the EntityMentionEnhancementEngine with the ReferencedSiteEntityTaggingEnhancementEngine
 - remove the CachingDereferencerEngine
 - replace the EntityCacheProvider with Entityhub functionality or provide an EntityCacheProvider implementation based on the Entityhub


BTW: I have added the checks for the configured ReferencedSiteEntityTaggingEnhancementEngine and the dbPedia ReferencedSite to the EnhancerTestBase.checkEnginesReady() method with revision #1082095

      was (Author: rwesten):
    I would rather do that within STANBOL-92, because this issue is about packing also a local index that can be used in combination with the ReferencedSiteEntityTaggingEnhancementEngine. Than such an integration test can run offline and there would be no danger to make Hudson unhappy if the SPARQL service at dbpedia.org is unavailable.

In addition as soon as STANBOL-92 is resolved we can also
 - remove the Autotagger
 - replace the EntityMentionEnhancementEngine with the ReferencedSiteEntityTaggingEnhancementEngine
 - remove the CachingDereferencerEngine
 - replace the EntityCacheProvider with Entityhub functionality provide an EntityCacheProvider implementation based on the Entityhub


BTW: I have added the checks for the configured ReferencedSiteEntityTaggingEnhancementEngine and the dbPedia ReferencedSite to the EnhancerTestBase.checkEnginesReady() method with revision #1082095
  
> Provide Default Configuration and Automatic Initialization for the Entityhub in the Stanbol Enhancer Full Launcher
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: STANBOL-115
>                 URL: https://issues.apache.org/jira/browse/STANBOL-115
>             Project: Stanbol
>          Issue Type: Improvement
>          Components: Enhancer, Entity Hub
>            Reporter: Rupert Westenthaler
>
> The Stanbol Enhancer Full Launcher includes the
>  - Entityhub and
>  - Referenced Site based Entity Tagging Enhancement Engine
> both currently require a manually configuration by the User.
> In addition if the User wants to use the Solr to cache local Entities he needs to run a SolrServer or provide a Solr Configuration on the local file system to run an EmbeddedSolrServer.
> Details are described in this Mail:
>   http://mail-archives.apache.org/mod_mbox/incubator-stanbol-dev/201103.mbox/%3cAANLkTin07KdaUZZFf5pi1LjYWW9hoPM0-gK3NF7GCDeT@mail.gmail.com%3e
> This needs to be improved by
> (1) providing a default configuration using Sling's org.apache.sling.launchpad.installer bundle (see http://issues.apache.org/jira/browse/STANBOL-110)
> (2) adapt the Entityhub it configure automatically based on the provided configuration. Especially add functionality to the SolrYard implementation that it can configure a SolrServer automatically based on the provided configuration.
> The goal is to have the Entityhub and the Referenced Site based Entity Tagging Enhancement Engine ready to be used without any additional configuration by the user when starting the full Stanbol Enhancer launcher jar the first time.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira