incubator-jena-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claude Warren (JIRA)" <>
Subject [jira] [Updated] (JENA-236) Allow Service XML Parsing error to cancel the query on a per query basis
Date Thu, 03 May 2012 08:18:06 GMT


Claude Warren updated JENA-236:

    Attachment: JENA-236-1.txt

Patch to use a context symbol (finishOnXmlStreamError) to cause XML Stream errors to signal
hasNext() to return false rather than aborting the entire query.

This is not per query as noted in the improvement title, nor does it take into account Silent,
cancelAllowDrain or JENA-93 changes.
> Allow Service XML Parsing error to cancel the query on a per query basis
> ------------------------------------------------------------------------
>                 Key: JENA-236
>                 URL:
>             Project: Apache Jena
>          Issue Type: Improvement
>          Components: ARQ
>    Affects Versions: ARQ 2.9.0
>         Environment: All
>            Reporter: Claude Warren
>              Labels: features
>         Attachments: JENA-236-1.txt
> Currently an XML parsing error may occur on a hasNext() call on a Sparql service query.
 The result is that the entire query (not just the service call) fails.
> The goal of this improvement is to capture the XML parsing error and return false for
the hasNext().  The result being that data errors will be silently ignored.  This should be
done on a per endpoint basis.  Perhaps as an onParseErrorCancel flag.
> I think there is an interplay of several flags in this request:
> 1) SILENT service parameter.  If silent is true should this also be true by default?
(I think not, but perhaps a system setting to make that the case)
> 2) cancelAllowDrain.  If the error occurs should the cancel flag be raised? (I think
not, but again perhaps a per service call flag to enable this)
> 3) JENA-93 discusses changing cancelAllowDrain to be a per endpoint setting.  If that
is the case it may apply here as well.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message