You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Stian Soiland-Reyes (JIRA)" <ji...@apache.org> on 2013/08/22 13:39:52 UTC
[jira] [Updated] (JENA-520) NullPointerException in
IO_Jena.resetJena()
[ https://issues.apache.org/jira/browse/JENA-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stian Soiland-Reyes updated JENA-520:
-------------------------------------
Description:
IO_JenaReaders.resetJena() (called by org.apache.jena.riot.IO_Jena.resetJena()) - threw a NullPointerException.
This is because it calls Property.setProperty("RDF/JSON", null) which does not allow null as value.
My suggested patch is at https://github.com/apache/jena/pull/2/files
This patch also fixes the bug JENA-521 in that other readers and writers like RDF/XML and RDF/XML-Abbrev were not reset.
was:
IO_JenaReaders.resetJena() (called by org.apache.jena.riot.IO_Jena.resetJena()) - threw a NullPointerException.
This is because it calls Property.setProperty("RDF/JSON", null) which does not allow null as value.
My suggested patch is at https://github.com/apache/jena/pull/2/files
This patch also fixes a bug in that other readers and writers like RDF/XML and RDF/XML-Abbrev were not reset.
> NullPointerException in IO_Jena.resetJena()
> -------------------------------------------
>
> Key: JENA-520
> URL: https://issues.apache.org/jira/browse/JENA-520
> Project: Apache Jena
> Issue Type: Bug
> Components: RIOT
> Affects Versions: Jena 2.10.1
> Reporter: Stian Soiland-Reyes
> Priority: Minor
>
> IO_JenaReaders.resetJena() (called by org.apache.jena.riot.IO_Jena.resetJena()) - threw a NullPointerException.
> This is because it calls Property.setProperty("RDF/JSON", null) which does not allow null as value.
> My suggested patch is at https://github.com/apache/jena/pull/2/files
> This patch also fixes the bug JENA-521 in that other readers and writers like RDF/XML and RDF/XML-Abbrev were not reset.
--
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