[jira] [Commented] (DAFFODIL-1959) EXIficient Inputter and outputter for XML EXI representation

["Dave Thompson (Jira)" <ji...@apache.org>]

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

Dave Thompson commented on DAFFODIL-1959:
-----------------------------------------

Verification of fixes for issues identified from the initial non-schema aware implementation and the initial release of the schema-aware implementation.

Verified the specified commit (commit 6270f42f65c295a85baa733503f82c712062700c) is included in the latest pull from the daffodil repository.

Verified changes identified in commit comment were implemented.

Verified the all affected daffodil subproject sbt test suites execute successfully including the added tests.

Verified unparse errors experienced on sevearl data formats no longer occur. Verified anomalies identifed between source and resulting unparsed files have been resolved and no longer occur. 

Ran parse/unparse on nightly performance test data using initial implementation of the -I exisa (schema-aware) option processing. Of the 22 data formats 11 failed to parse rendering 1 of the following exceptions:

1)  com.siemens.ct.exi.core.exceptions.EXIException: XML Schema document (null) not found. (9 formats, see attachment)

2)  Exception in thread "main" java.lang.StackOverflowError  (2 formats, see attachment)

Documented results and attached to ticket comment.[^EXISA Parse-Unparse_Result.docx]

> EXIficient Inputter and outputter for XML EXI representation
> ------------------------------------------------------------
>
>                 Key: DAFFODIL-1959
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-1959
>             Project: Daffodil
>          Issue Type: New Feature
>          Components: Back End
>    Affects Versions: 2.1.0
>            Reporter: Mike Beckerle
>            Priority: Critical
>              Labels: beginner
>             Fix For: 3.4.0
>
>         Attachments: EXI Parse-Unparse Results.docx, EXISA Parse-Unparse_Result.docx
>
>
> Create EXI (dense binary XML) representation using an EXI-specific InfosetInputter and InfosetOutputter.
> These would be very similar to the XML InfosetInputter and Outputter - as EXI libraries such as EXIfficient https://github.com/EXIficient/exificient already have SAX/StAX, APIs, etc. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)