You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@daffodil.apache.org by "Josh Adams (Jira)" <ji...@apache.org> on 2022/11/29 19:49:00 UTC

[jira] [Resolved] (DAFFODIL-2750) Add option to encode/decode EXI files

     [ https://issues.apache.org/jira/browse/DAFFODIL-2750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Josh Adams resolved DAFFODIL-2750.
----------------------------------
      Assignee:     (was: Josh Adams)
    Resolution: Fixed

This has been added in commit 06701b1b833cc24159608e5315808dcb89c69771

> 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
>            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)