[
https://issues.apache.org/jira/browse/DAFFODIL-2896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olabusayo Kilo resolved DAFFODIL-2896.
--------------------------------------
Fix Version/s: 4.0.0
(was: 3.7.0)
Resolution: Fixed
Fixed in dad8c6d691e92ea62cd2f8e3ef1e7898b65f8a23
> validationMode=full enables Daffodils limited validation
> --------------------------------------------------------
>
> Key: DAFFODIL-2896
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2896
> Project: Daffodil
> Issue Type: Bug
> Components: Back End
> Reporter: Steve Lawrence
> Assignee: Olabusayo Kilo
> Priority: Major
> Fix For: 4.0.0
>
>
> Daffodil has three validation modes: off, limited, and full. "Limited"
> enables Daffodils internal validation during parsing and "full" enables
> Xerces validation at the end of parsing. However, "full" also enables
> Daffodils limited validation, so we incur extra overhead with full validation.
> We should change full validation so it only does Xerces validation. Note that
> this change is not backwards compatible and could potentially break tests
> that use full validation but specifically look for Daffodil validation
> messages.
> Alternatively, we may want to consider adding a new validation mode that only
> enables xerces. Then "full" could keep its current behavior of validating
> with Daffodil and Xerces. This has the added benefit that we can get complete
> test coverage of both validation mechanisms without having to duplicate tests.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
