[jira] [Commented] (DAFFODIL-2373) Validation 'fatal' option needed - so that validation errors cause parse to fail.

["Mike Beckerle (Jira)" <ji...@apache.org>]

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

Mike Beckerle commented on DAFFODIL-2373:
-----------------------------------------

This would require API and CLI change to enable this new mode.

 

Suggest --validationAction with values "warning" or "fatal" for the CLI, and setValidationAction(...) as the API call.

This would require --validation on or limited.

> Validation 'fatal' option needed - so that validation errors cause parse to fail.
> ---------------------------------------------------------------------------------
>
>                 Key: DAFFODIL-2373
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2373
>             Project: Daffodil
>          Issue Type: New Feature
>          Components: Back End
>    Affects Versions: 2.7.0
>            Reporter: Mike Beckerle
>            Priority: Major
>             Fix For: 3.0.0
>
>
> We need a mode that is equivalent to having an assert call checkConstraints(.) on all simple elements, and check the max/min occurs bounds on arrays.
> This model escalates a validation 'limited' validation error into a parse error for purposes of backtracking and pass/fail of the parse.
> These should still be labeled as "Validation Error", but perhaps should print "Parse Error (Validation Error)" so that TDML tests can look for either string.
>  
>  
>  
>  
>  



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