You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@daffodil.apache.org by "Steve Lawrence (JIRA)" <ji...@apache.org> on 2019/06/18 18:40:01 UTC

[jira] [Resolved] (DAFFODIL-2150) Excessive emptyElementParsePolicy warnings

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

Steve Lawrence resolved DAFFODIL-2150.
--------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.4.0

Fixed in commit b8338d7c7f56f335a25d945da0824529c126af6c

> Excessive emptyElementParsePolicy warnings
> ------------------------------------------
>
>                 Key: DAFFODIL-2150
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2150
>             Project: Daffodil
>          Issue Type: Bug
>          Components: Diagnostics
>            Reporter: Steve Lawrence
>            Assignee: Steve Lawrence
>            Priority: Major
>             Fix For: 2.4.0
>
>
> If a schema has a need for the emptyElementParsePolicy property, but it's not defined, you end up with a lot of duplicate warnings like:
> {quote}
> [warning] Schema Definition Warning: Property 'dfdl:emptyElementParsePolicy' is required but not defined, using tunable 'treatAsEmpty' by default.
> {quote}
> This warning is helpful, but it is repeated for what seems like every element in the schema, which makes it not very user friendly.
> Maybe we should only record the first instance of each WarnID, but add a warning that other instances were hidden. And add a tunable flag to enable recording of all instances if the user wants it all.
> Additinoally or alternatively, we might want to think about not recording warnings at all for extensions. They are extensions after all. If someone's schema is DFDL v1.0 compliant, there's an argument that we shouldn't output warnings for things related to extensions. 



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