[
https://issues.apache.org/jira/browse/DAFFODIL-2750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Adams resolved DAFFODIL-2750.
----------------------------------
Resolution: Fixed
I've added a SAXErrorHandler and a Transformer.ErrorListener to the CLI tool
and that cleans up most of the error output that was getting printed out. The
last stack trace that is still coming through will require a SAX update or
Exificient update. I've actually opened a pull request for Exificient to
handle this error case better:
https://github.com/EXIficient/exificient/issues/33
The changes to the CLI tool were done in commit:
0638f3e390f648525c806cafce465f09f8e7dfb5
> Add option to encode/decode EXI files
> -------------------------------------
>
> Key: DAFFODIL-2750
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2750
> Project: Daffodil
> Issue Type: New Feature
> Components: CLI
> Affects Versions: 3.4.0
> Reporter: Josh Adams
> Assignee: Josh Adams
> Priority: Major
> Fix For: 3.5.0
>
>
> It is rather cumbersome to encode/decode schema aware EXI files as they need
> access to the Daffodil XML resolver in order to import/include schemas
> correctly. Having a simple:
> "daffodil encodeEXI -s /path/to/schema /path/to/file.xml"
> to convert an XML file to an EXI file will be very helpful for testing. A
> decodeEXI command would also be added.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
