[
https://issues.apache.org/jira/browse/DAFFODIL-2909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17853665#comment-17853665
]
Steve Lawrence commented on DAFFODIL-2909:
------------------------------------------
One potential fix is to change the TDML runner so it uses the output of the
ScalaInfosetOutputter to comparing expected and actual infosets, since that
doesn't implement stringAsXml. This would mean we can't test stringAsXml using
the TDML runner, but allowing a dfdlInfoset to contains any XML feels like it
could be fragile since generally we only expect DFDL infosets and not
everything that could possibly be in XML.
> stringAsXML: TDML XML Comparison fails on mixed content XML or other
> non-DFDL-conforming XML
> --------------------------------------------------------------------------------------------
>
> Key: DAFFODIL-2909
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2909
> Project: Daffodil
> Issue Type: Bug
> Components: Infrastructure, QA, TDML Runner
> Reporter: Mike Beckerle
> Priority: Major
>
> The stringAsXML feature allows embedding arbitrary XML content into the XML
> output from a Daffodil parse.
> When the TDML runner compares output to expected output, this fails because
> the output is not from a DFDL parse, but is an embedded string of XML.
> That embedded string can use many things that DFDL doesn't normally create
> such as XML mixed content, XML attributes, etc.
> The XML diff comparison fails on this.
> Hence, TDML tests cannot be created when stringAsXML is used, unless you are
> lucky and the embedded XML string just happens to not use XML attributes,
> mixed content, or anything else that isn't part of the DFDL subset of XSD.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
