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

Dave Thompson closed DAFFODIL-2638.
-----------------------------------

Verified the specified commit (commit 97ea8f75de522d9d172f94a83f68fb6a7545b72c) 
is included in the latest pull from the daffodil repository.

Verified, via review, changes identified in the commit comment were 
implemented. 

Verified the affected daffodil subproject sbt test suites executed 
successfully, including the added tests.

Verified the nightly test suite executes successfully with no unexpected 
failures.

> Property to suppress warnings only for a specific place in the schema
> ---------------------------------------------------------------------
>
>                 Key: DAFFODIL-2638
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2638
>             Project: Daffodil
>          Issue Type: New Feature
>          Components: Front End
>    Affects Versions: 3.2.1
>            Reporter: Mike Beckerle
>            Priority: Major
>             Fix For: 3.9.0
>
>
> We can currently suppress warnings globally, using a config file. 
> We have found that it is sometimes important to make a DFDL schema create a 
> structure, but we always want that structure to be invalid. 
> This enables capture of bad data into human readable XML elements, for 
> example, but insures that data cannot be mistaken for valid data. 
> So we do things like this:
> {code:java}
> <simpleType name="invalidNoData" 
>   dfdl:lengthKind="explicit" dfdl:length="0"> <!-- always length 0 -->
>   <restriction base="xs:hexBinary">
>     <minLength value="1"/> <!-- always invalid because must be length 1 --> 
>   </restriction>
> </simpleType> {code}
> This generates a schema definition warning. 
> Now we get these for every unit test, and they clutter the diagnostics, so we 
> use a config file to suppress this warning.
> But other than in locations like this, anywhere else in the schema, if you do 
> this sort of thing, it would be a mistake. So we really only want to suppress 
> the warning locally on this simple type definition.
> A property allowing specification of a list of warnings to suppress would be 
> helpful.
>  



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

Reply via email to