[
https://issues.apache.org/jira/browse/DAFFODIL-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olabusayo Kilo updated DAFFODIL-3010:
-------------------------------------
Summary: Handle Validation for IBM Cross Tester for new Validator API
(was: Handl eValidation for IBM Cross Tester for new Validator API)
> Handle Validation for IBM Cross Tester for new Validator API
> ------------------------------------------------------------
>
> Key: DAFFODIL-3010
> URL: https://issues.apache.org/jira/browse/DAFFODIL-3010
> Project: Daffodil
> Issue Type: Bug
> Components: TDML Runner
> Affects Versions: 3.11.0
> Reporter: Olabusayo Kilo
> Priority: Major
>
> Note that the tdml processor could be used by the IBM DFDL cross tester.
> withValidator really is not a Daffodil specific thing. We have two options
> The right thing to do might be to modify the IBM DFDL cross tester so that it
> looks for our specific validators and disables validation if it's
> NoValidator, and enables it if it's anything else. Alternatively, maybe we
> need a different API for the {{{}TDMLDFDLProcessor{}}}. We need to figure out
> how to handle validation in a way that works better for the IBM DFDL TDML
> processor that doesn't need to know about our internal Validator API.
> Another option is the TDML Runner still only understands on, liimited, and
> off, and then it is up to the IBM TDML Professor and Daffodil TDML Processor
> to convert that to their own kind of validation. The Daffodil one will use
> the Validator API. The IBM one will just set a validation boolean.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
