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

Steve Lawrence commented on DAFFODIL-2904:
------------------------------------------

In addition to sax vs non-sax, we probably want an option that allows disabling 
the TDMLInfosetInputter/Outtputer stuff that checks that every infoset 
inputter/outputter gives the same results (that's really what the sax-api in 
the TDML runner is about--checking for consistency with the other API, not so 
much testing the sax API itself). All these extra infoset inputters and SAX API 
is the default behavior for the TDML runner, and probably adds decent overhead 
to DFDL Schema projects that we should probably try to avoid. We've had this 
long enough with no real issues that I think we can be pretty confident that 
they all have the same behavior. 

So maybe what we really need is a single config flag where one mode is the 
non-sax API with a single infoset inputter/outputter, and another mode that 
enables the current behavior. We set the default to the former mode for 
efficiency, and the latter mode can be enabled during CI or regression testing 
to ensure our different infoset inputter/outputter behaviors remain consistent 
with no regressions.

> trace and TDML runner don't work together because of SAX and non-SAX API 
> being tested
> -------------------------------------------------------------------------------------
>
>                 Key: DAFFODIL-2904
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2904
>             Project: Daffodil
>          Issue Type: Bug
>          Components: Debugger, TDML Runner
>    Affects Versions: 3.7.0
>            Reporter: Mike Beckerle
>            Priority: Major
>
> If you turn on trace for a TDML test, it's quite confusing because the parse 
> happens twice. Once for the non-SAX API, one for the SAX API. 
> That's good for insisting they behave identically, but useless for tracing. 
> If tracing/debugging is on, we should only parse once using one API for the 
> TDML test. 



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

Reply via email to