You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "Dave Thompson (Jira)" <ji...@apache.org> on 2021/05/20 20:02:04 UTC

[jira] [Closed] (DAFFODIL-1967) Support --stream option for CLI unparse subcommands

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

Dave Thompson closed DAFFODIL-1967.
-----------------------------------

Closing due to no activity.
The specified commit was in the latest pull from the daffodil repository.
The code was peer reviewed per process.
If an issue occurs with the updates it will be addressed in a new tickets.

> Support --stream option for CLI unparse subcommands
> ---------------------------------------------------
>
>                 Key: DAFFODIL-1967
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-1967
>             Project: Daffodil
>          Issue Type: New Feature
>          Components: CLI
>    Affects Versions: 2.2.0
>            Reporter: Steve Lawrence
>            Assignee: Steve Lawrence
>            Priority: Major
>             Fix For: 2.2.0
>
>
> The --stream option for the parse subcommand currently outputs repetitions of XML data, e.g.
> {code:xml}
> <foo>...</foo>
> <foo>...</foo>
> <foo>...</foo>
> {code}
> Since there is no root element, this is not valid XML data and the libraries we use to parse the XML string throw and error. So, in order support streaming XML data into unparsing we need to manually split the XML before giving it to the XML parsing libraries. Parsing XML ourselves and just not caring about not having a root element is an option, but might be more effort than it is worth. Another option is to output some sort of delimiter in between each XML and just split the data on that. Extra care needs to be done to ensure that we do not split if the XML content contains that delimiter.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)