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/01/20 21:46:00 UTC

[jira] [Updated] (DAFFODIL-697) Java API: ProcessorFactory's setDistinguishedRootNode method does not appear to work.

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

Dave Thompson updated DAFFODIL-697:
-----------------------------------
    Labels:   (was: reverify)

> Java API: ProcessorFactory's setDistinguishedRootNode method does not appear to work.
> -------------------------------------------------------------------------------------
>
>                 Key: DAFFODIL-697
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-697
>             Project: Daffodil
>          Issue Type: Bug
>          Components: API
>            Reporter: Jessie Chab
>            Priority: Minor
>
> I copied testJavaAPI3 in 
> daffodil-core/src/test/java/edu/illinois/ncsa/daffodil/example/TestJavaAPI.java
> and added a new element to 
> daffodil-core/src/test/resources/test/japi/mySchema3.dfdl.xsd
> I modified the test (new test is testJavaAPI4) to reference my new element (e4) and my new data file (myData2.bat)
> When I run the test it still seems to be referencing element e3, the first element in the schema. When I swap e3 and e4 in the schema, all tests that reference that schema use e4 - the first element.
> Steve suggested trying the compiler's setDistinguishedRootNode before running compile, and that worked with no problems. It only seems to be the ProcessorFactory's setDistinguishedRootNode method that isn't working.
> I commented out the failing test (testJavaAPI4) and added the passing test that uses the compiler's method (testJavaAPI4b)



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