I created https://issues.apache.org/jira/browse/STANBOL-698 for this issue.

BR,
David

On Sun, Jul 22, 2012 at 8:40 PM, David Riccitelli <[email protected]>wrote:

> Hello,
>
> 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
> '&lt;urn:content-item-sha1-c153a98f2f30dd79232ba6af3f71f30e4e6a0093&gt;'
> 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
>
> BR,
> David
>
> --
> David Riccitelli
>
>
> ********************************************************************************
> InsideOut10 s.r.l.
> P.IVA: IT-11381771002
> Fax: +39 0110708239
> ---
> LinkedIn: http://it.linkedin.com/in/riccitelli
> Twitter: ziodave
> ---
> Layar Partner 
> Network<http://www.layar.com/publishing/developers/list/?page=1&country=&city=&keyword=insideout10&lpn=1>
>
> ********************************************************************************
>
>


-- 
David Riccitelli

********************************************************************************
InsideOut10 s.r.l.
P.IVA: IT-11381771002
Fax: +39 0110708239
---
LinkedIn: http://it.linkedin.com/in/riccitelli
Twitter: ziodave
---
Layar Partner 
Network<http://www.layar.com/publishing/developers/list/?page=1&country=&city=&keyword=insideout10&lpn=1>
********************************************************************************

Reply via email to