You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "Mike Beckerle (Jira)" <ji...@apache.org> on 2022/03/25 15:38:00 UTC
[jira] [Commented] (DAFFODIL-2615) group sharing causes obscure unparser runtime error
[ https://issues.apache.org/jira/browse/DAFFODIL-2615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512446#comment-17512446 ]
Mike Beckerle commented on DAFFODIL-2615:
-----------------------------------------
Added to 3.4.0 release target because many DFDL schema projects are having to work around this by duplicating (and therefore not sharing) what would otherwise be shared groups.
> 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.2.1
> Reporter: Mike Beckerle
> Priority: Major
> Fix For: 3.4.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.1#820001)