You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@daffodil.apache.org by "Dave Thompson (JIRA)" <ji...@apache.org> on 2018/04/10 13:20:00 UTC

[jira] [Closed] (DAFFODIL-1874) Incorrect warning message about default value and no empty representation

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

Dave Thompson closed DAFFODIL-1874.
-----------------------------------

Pulled the latest updates from the incubator-daffodil repository and verified the updates included the specified commit, 075084f5a825bde3168b8e89a02c7e58404cc325.

Verified that the warning messages displyed during NACHA format processing now reflect the specified change. Verified that all sbt tests execute successfully. Verified that all nightly tests execute successfully.

> Incorrect warning message about default value and no empty representation
> -------------------------------------------------------------------------
>
>                 Key: DAFFODIL-1874
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-1874
>             Project: Daffodil
>          Issue Type: Bug
>          Components: Middle &quot;End&quot;
>    Affects Versions: 2.0.0
>            Reporter: Michael Beckerle
>            Assignee: Dave Thompson
>            Priority: Major
>             Fix For: 2.1.0
>
>
> NACHA schema (on DFDLSchemas github) has a ticket about suppressing a warning that we get for almost every element in that schema:
> https://github.com/DFDLSchemas/NACHA/issues/2
> This is the warning we get:
> {{{Schema Definition Warning: Element has no empty representation so cannot have XSD default='0' as a default value.
> Schema context: element reference {ach:2013}PriorityCode Location line 55 column 18 in file:/home/mbeckerle-unencrypted/DFDLSchemas/NACHA/2013/nacha_records.xsd}}}
> The warning is misleading, it should say that for an element with no empty rep the default value can only be applied on unparsing (where the criteria is that the element is not in the infoset).
> AND that corrected warning, which we'll still get for every element of NACHA, needs to be suppressable for a schema like NACHA where otherwise you get dozens of them. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)