[
https://issues.apache.org/jira/browse/DAFFODIL-723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16637670#comment-16637670
]
Michael Beckerle commented on DAFFODIL-723:
-------------------------------------------
Thoughts on better design for this:
testCase should have an attribute implementations="..."
testSuite should have defaultImplementations="..."
the defaultImplementationsDefault should be 'daffodil'
Additional implementations are specified by providing a class name - to be
found in jars on the class path and dynamically loaded.
The class must implement a Java Interface (or Scala Trait), that defines an
abstract interface to a DFDL processor that can be implemented as a wrap-around
IBM DFDL, or any other implementation. Likely this trait looks like the
Daffodil API features that the TDML runner uses.
Presumably for the IBM implementation this adapter class would then dynamically
load the IBM jars as well, (or in the case of a C/C++ implementation of DFDL,
would include JNI code for invoking it, starting it as a dynamic library, etc.)
> Compatibility: Cross Validation of DFDL and IBM implementation
> --------------------------------------------------------------
>
> Key: DAFFODIL-723
> URL: https://issues.apache.org/jira/browse/DAFFODIL-723
> Project: Daffodil
> Issue Type: Improvement
> Components: Compatibility, Infrastructure, QA, TDML Runner
> Reporter: Andrew Seyler
> Priority: Major
> Labels: ForInteroperabilityTest
>
> run our suite of tests against the IBM implementation and note
> inconsistencies.
> This will require significant test harness type development.
> We'll call this Phase 1.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
