You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by "Alessandro Adamou (JIRA)" <ji...@apache.org> on 2015/06/18 19:16:00 UTC
[jira] [Resolved] (STANBOL-1427) Make failed import policy
configurable
[ https://issues.apache.org/jira/browse/STANBOL-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alessandro Adamou resolved STANBOL-1427.
----------------------------------------
Resolution: Done
If we want to extend this configuration to the clients, a separate ticket will be opened
> Make failed import policy configurable
> --------------------------------------
>
> Key: STANBOL-1427
> URL: https://issues.apache.org/jira/browse/STANBOL-1427
> Project: Stanbol
> Issue Type: Improvement
> Components: Ontology Manager
> Reporter: Alessandro Adamou
> Assignee: Alessandro Adamou
> Labels: owl
>
> right now the ontologymanager always fails if an import is missing, but still it does store the dependencies it was able to load until the failure occurred.
> It might be worth being able to tell the ontology providers to still be able to load ontologies even if an import fails. Let's start with a Component Configuration first.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)