[
https://issues.apache.org/jira/browse/DAFFODIL-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17167181#comment-17167181
]
Josh Adams commented on DAFFODIL-2375:
--------------------------------------
After doing a fair amount of digging, I've narrowed down this issue to the fact
that there are empty sequences in the choice that only have a call to
setVariable in them, no actual elements. If there is a simple element inside
these sequences, then this test works fine.
I guess we need to decide if having empty sequences (which don't show up at all
in the infoset) unparse as I was expecting is correct behaviour or not.
Currently, it seems like it tries to unparse this choice with empty sequences,
but for some reason it keeps trying to unparse the first branch of the choice.
> Multiple calls to setVariable when unparsing choice branches
> ------------------------------------------------------------
>
> Key: DAFFODIL-2375
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2375
> Project: Daffodil
> Issue Type: Bug
> Components: Back End
> Affects Versions: 2.7.0
> Reporter: Josh Adams
> Assignee: Josh Adams
> Priority: Major
> Fix For: 3.0.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Discovered this issue while working on a schema project.
> While the schema parses fine, for some reason multiple SetVariable parsers
> are getting instantiated for the same variable, which causes a double-set
> error to occur.
>
> See [https://github.com/apache/incubator-daffodil/pull/401] for a test that
> demonstrates this issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
