[
https://issues.apache.org/jira/browse/JENA-618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13860284#comment-13860284
]
Andy Seaborne commented on JENA-618:
------------------------------------
The placement of the call to {{IO_JenaReaders.wireIntoJena()}} is deceptive.
This is called implicitly when Jena initialises readers.
See {{LangRDFXML$ErrorHandlerBridge}} for the policy of mapping old style error
handling to new. See also the javadoc for
{{org.apache.jena.riot.system.ErrorHandler#error}}.
The issue is the ARP ERROR case. Should ERROR terminate parsing or not?
Default in RIOT is to stop. (This is configurable with effort : JENA-518).
Why is it an ERROR when the code recovers and continues?
See test2.java for an example.
> calling IO_JenaReaders.wireIntoJena() and RDFReaderFImpl.reset() does not
> reset the reader properly
> ---------------------------------------------------------------------------------------------------
>
> Key: JENA-618
> URL: https://issues.apache.org/jira/browse/JENA-618
> Project: Apache Jena
> Issue Type: Bug
> Affects Versions: Jena 2.11.1
> Reporter: Claude Warren
> Priority: Minor
> Attachments: test.java, test2.java
>
>
> Calling IO_JenaReaders.wireIntoJena() and then RDFReaderFImpl.reset() yeilds
> an RDF reader that does not fail when a relative URI is read.
> It does report a warning if logging is enabled.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
