You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@daffodil.apache.org by "Michael Beckerle (JIRA)" <ji...@apache.org> on 2019/06/10 17:59:00 UTC

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

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

Michael Beckerle commented on DAFFODIL-2150:
--------------------------------------------

This new property is *not* yet something we want everyone to embed in schemas to shut up the warning. Because it is subject to change.

I suggest we just shut off this warning. We have a tunable where we can make this property required in the future, at which point it's reasonable for us to have it be defaulted if not found. But for now we should just silently default it I think.

> 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
>            Priority: Major
>
> 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)