You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@daffodil.apache.org by "Michael Beckerle (JIRA)" <ji...@apache.org> on 2019/02/21 23:30:00 UTC

[jira] [Commented] (DAFFODIL-935) DFDL encodingErrorPolicy='error' feature

    [ https://issues.apache.org/jira/browse/DAFFODIL-935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16774591#comment-16774591 ] 

Michael Beckerle commented on DAFFODIL-935:
-------------------------------------------

This is partly fixed. In order to run IBM-created DFDL schemas, we accept this policy, but we don't implement it. We implement replace behavior always.

This is ok as a stop-gap because most schemas aren't depending on actually backtracking due to decode errors. It's just that IBM implemented the 'error' behavior, and so set that in their schemas as the default behavior.

We can get through most interoperability testing without actually implementing 'error' behavior.

> DFDL encodingErrorPolicy='error' feature
> ----------------------------------------
>
>                 Key: DAFFODIL-935
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-935
>             Project: Daffodil
>          Issue Type: New Feature
>          Components: Back End, Compatibility, DFDL Language
>    Affects Versions: s13
>            Reporter: Michael Beckerle
>            Priority: Major
>              Labels: ForInteroperabilityTest
>             Fix For: 2.4.0
>
>
> 0.13.0 has encodingErrorPolicy="replace". (DFDL-893). This is to implement the much more challenging precise-error feature. This creates performance challenges because one cannot buffer-ahead character conversion from bytes in the obvious ways that say, java.io.BufferedReader does.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)