You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "Dave Thompson (Jira)" <ji...@apache.org> on 2021/05/20 12:35:09 UTC
[jira] [Closed] (DAFFODIL-2135) Array index not maintained
properly. Causes nillable failures among others.
[ https://issues.apache.org/jira/browse/DAFFODIL-2135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dave Thompson closed DAFFODIL-2135.
-----------------------------------
Closed due to no activity and no re-occurrence. If the issue re-occurs the ticket can be reopened or addressed in a new one.
> Array index not maintained properly. Causes nillable failures among others.
> ---------------------------------------------------------------------------
>
> Key: DAFFODIL-2135
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2135
> Project: Daffodil
> Issue Type: Bug
> Components: Back End
> Affects Versions: 2.4.0
> Reporter: Mike Beckerle
> Assignee: Dave Thompson
> Priority: Major
> Fix For: 2.4.0
>
>
> Since git hash 53d6b4f342140f9a807ee1ca087dbeaf0367ade7 which was merged 2019-05-22, some formats no longer work.
> For one such format, the reason is clear. nillable optional elements with zero-length aren't being treated correctly.
> Specifically nilValue="%ES;" and nilValueDelimiterPolicy="none"
> An element that is nillable, but also minOccurs 0 maxOccurs 1 should appear in the infoset as nilled, but current behavior is it is being omitted.
> Even when the element is optional, nil takes precedence over optionality.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)