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

Olabusayo Kilo resolved DAFFODIL-2735.
--------------------------------------
    Resolution: Won't Fix

One could use escalateWarningsToErrors tunable which escalates all warnings to 
error, and then use suppressSchemaDefinitionWarnings tunable to suppress the 
warnings one doesn't care about being errors.

> extension property to selectively escalate warnings to errors
> -------------------------------------------------------------
>
>                 Key: DAFFODIL-2735
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2735
>             Project: Daffodil
>          Issue Type: New Feature
>          Components: Front End
>    Affects Versions: 3.3.0
>            Reporter: Mike Beckerle
>            Assignee: Olabusayo Kilo
>            Priority: Major
>
> Daffodil issues warnings about things like 
>  * when two element children differ only by namespace so that JSON (or other 
> form that does not support namespaces) won't work.
> Such a warning should be something we can escalate to an error, by way of a 
> property in the schema - such property indicates an intention to maintain the 
> schema in a manner that keeps it compatible with JSON (or whatever).
> There are other warnings that should also be escalated to errors. (see 
> DAFFODIL-2736, DAFFODIL-2737)
> One should be able to selectively choose which warnings to escalate to 
> errors. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to