You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Andy Seaborne (JIRA)" <ji...@apache.org> on 2018/05/04 09:12:00 UTC
[jira] [Commented] (JENA-1288) Reduce dependency on the Xerces jar.
[ https://issues.apache.org/jira/browse/JENA-1288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16463598#comment-16463598 ]
Andy Seaborne commented on JENA-1288:
-------------------------------------
Further update:
Apache Xerces is no longer a dependency requirement for Apache Jena. JENA-1537 extracts the Xerces validation code for Jena's use and removes the dependency on Xerces as the XML parser.
> Reduce dependency on the Xerces jar.
> ------------------------------------
>
> Key: JENA-1288
> URL: https://issues.apache.org/jira/browse/JENA-1288
> Project: Apache Jena
> Issue Type: Task
> Affects Versions: Jena 3.2.0
> Reporter: Andy Seaborne
> Assignee: Andy Seaborne
> Priority: Minor
> Fix For: Jena 3.3.0
>
>
> There are facilities in the standard JDK that can be used instead of directly calling Xerces, specifically {{DatatypeConverter}}. With these changes, only one class relies on Xerces directly, {{XSDDatatype}}.
> We have to be careful though - it is not perfect. I found that {{parseByte}} calls {{parseInt}} and casts the result to a java {{byte}} so it passes "300" and "3000" which are not valid byte lexical forms.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)