You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "Josh Adams (Jira)" <ji...@apache.org> on 2019/12/30 18:02:00 UTC
[jira] [Resolved] (DAFFODIL-2261) Optional first element in
unordered sequence fails to unparse
[ https://issues.apache.org/jira/browse/DAFFODIL-2261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh Adams resolved DAFFODIL-2261.
----------------------------------
Assignee: Dave Thompson (was: Josh Adams)
Resolution: Fixed
This has been fixed in commit 8712f7c43fb8fd3a6183561dfdd47aee1c632ee9
> Optional first element in unordered sequence fails to unparse
> -------------------------------------------------------------
>
> Key: DAFFODIL-2261
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2261
> Project: Daffodil
> Issue Type: Bug
> Components: Back End
> Affects Versions: 2.5.0
> Reporter: Josh Adams
> Assignee: Dave Thompson
> Priority: Major
> Fix For: 2.5.0
>
> Attachments: BE.dfdl.xsd, BE.tdml
>
>
> A user discovered an issue with optional elements inside unordered sequences. Specifically, when the first element of an unordered sequence has minOccurs="0" and does not have maxOccurs > 1, the unparse attempt will fail with the following error message:
> "Expected element start event for {}x, but received element end event for {}y."
> Attached is a test case demonstrating this behavior.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)