[
https://issues.apache.org/jira/browse/DAFFODIL-2615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Thompson closed DAFFODIL-2615.
-----------------------------------
Verified the specified commit (commit 7fd1117e9ab869182110803e8638d1e2b7659af8)
is included in the latest pull from the daffodil repository.
Verified, via review, the changes identified in the commit comment were
implemented.
Verified the affected daffodil subproject sbt test suites executed
successfully, including the uncommented and added tests.
Rolled back to a pre-fix commit, uncommented the commented test and verified
that the test failed as expected.
> group sharing causes obscure unparser runtime error
> ---------------------------------------------------
>
> Key: DAFFODIL-2615
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2615
> Project: Daffodil
> Issue Type: Bug
> Components: Back End, Middle "End"
> Affects Versions: 2.7.0, 3.3.0, 3.2.1
> Reporter: Mike Beckerle
> Priority: Major
> Fix For: 3.5.0
>
>
>
> While working on a large DFDL schema, ran into a problem where a group is
> being shared in 2 places.
> I get an obsure message at unparse time like this:
> "Unparser needed event for {}nackHeader but got (invalid) {}nackHeader"
> This element nackHeader is the element that appears immediately after *one*
> of the shared group references. The other one works fine.
> Making a copy of the shared group so that it is no longer shared eliminates
> the problem and is the workaround.
> I will endeavor to create a simplified scenario to reproduce.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
