You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by "Rupert Westenthaler (JIRA)" <ji...@apache.org> on 2014/04/17 08:41:20 UTC
[jira] [Updated] (STANBOL-1323) Change ConfigurationPolicy of all
EntityDereferencer and EntitySearcher ComponentFactories to OPTIONAL
[ https://issues.apache.org/jira/browse/STANBOL-1323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rupert Westenthaler updated STANBOL-1323:
-----------------------------------------
Fix Version/s: (was: 1.0.0)
> Change ConfigurationPolicy of all EntityDereferencer and EntitySearcher ComponentFactories to OPTIONAL
> ------------------------------------------------------------------------------------------------------
>
> Key: STANBOL-1323
> URL: https://issues.apache.org/jira/browse/STANBOL-1323
> Project: Stanbol
> Issue Type: Bug
> Components: Entityhub
> Reporter: Rupert Westenthaler
> Assignee: Rupert Westenthaler
> Fix For: 0.12.1
>
>
> All EntityDereferencer and EntitySearcher implementations (all of them in the entityhub.site.linkeddata module) have used ConfigurationPolicy.REQUIRE since the beginning. The idea was that instances created with this ComponentFactories do require a configuration. However that is not the intention of the annotation. The annotation defines if the factory needs a configuration. As this is not required the correct annotation is ConfigurationPolicy.OPTIONAL.
> Before STANBOL-1322 this was not an issue as the used Felix version had ignored the configuration policy for ComponentFactories. However after the version update this is no longer the case and the therefore no ComponentFactories for EntityDereferencer and EntitySearcher where created.
> Because of that no Entityhub ReferencedSite with configured EntitySearcher or EntityDereferencer could be created.
> To Solve this one needs to changte the ConfigurationPolicy annotation of all
> EntityDereferencer and EntitySearcher implementations from REQUIRE to OPTIONAL (the default).
--
This message was sent by Atlassian JIRA
(v6.2#6252)