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 2012/12/14 07:24:12 UTC
[jira] [Resolved] (STANBOL-698) issue with NaN in
http://www.w3.org/2001/XMLSchema#double
[ https://issues.apache.org/jira/browse/STANBOL-698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rupert Westenthaler resolved STANBOL-698.
-----------------------------------------
Resolution: Fixed
Assignee: Rupert Westenthaler
resolved after adding a unit test with http://svn.apache.org/viewvc?rev=1421683&view=rev
> issue with NaN in http://www.w3.org/2001/XMLSchema#double
> ---------------------------------------------------------
>
> Key: STANBOL-698
> URL: https://issues.apache.org/jira/browse/STANBOL-698
> Project: Stanbol
> Issue Type: Bug
> Components: Entityhub
> Affects Versions: entityhub-0.10.0-incubating
> Reporter: David Riccitelli
> Assignee: Rupert Westenthaler
> Attachments: NAN.txt, STANBOL-698.diff
>
>
> I recently ran into an issue [1]. It seems that sometimes values in resources declared as double, are eventually not numbers and the Resource2ValueAdapter [3] throws an exception:
> "A value is being adapted [mapped-class :: class java.lang.Double][literal :: NAN][literal data-type :: <http://www.w3.org/2001/XMLSchema#double>]."
> Shall we make the Resource2ValueAdapter check whether the literal value can actually be converted to the destination data-type?
> [1] Error 500 Enhancement Chain failed because of required Engine 'dbpediaLinking' failed with Message: Unable to process ContentItem '<urn:content-item-sha1-c153a98f2f30dd79232ba6af3f71f30e4e6a0093>' with Enhancement Engine 'dbpediaLinking' because the engine was unable to process the content (Engine class: org.apache.stanbol.enhancer.engines.entitytagging.impl.NamedEntityTaggingEngine)(Reason: For input string: "NAN")!
> [2] org.apache.stanbol.entityhub.model.clerezza.impl.Resource2ValueAdapter
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira