[
https://issues.apache.org/jira/browse/DAFFODIL-2135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16847897#comment-16847897
]
Michael Beckerle commented on DAFFODIL-2135:
--------------------------------------------
This bug renamed. Turned out not to be an issue with nils as expected but bugs
with arrayIndexStack push/pop.
> optional elements that are nillable, where nilValue is ES are being omitted,
> not nilled
> ---------------------------------------------------------------------------------------
>
> 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: Michael Beckerle
> Assignee: Michael Beckerle
> 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
(v7.6.3#76005)
