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 2020/01/02 18:01:00 UTC

[jira] [Commented] (DAFFODIL-2260) unparse array/optional with occursCountKind 'expression' evaluating to 1 or more, doesn't unparse

    [ https://issues.apache.org/jira/browse/DAFFODIL-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17006990#comment-17006990 ] 

Josh Adams commented on DAFFODIL-2260:
--------------------------------------

Is there a specific test that I can look at that is causing this issue?  At first glance, test AD000 in SequenceGroupl.tdml seems like it would cover this scenario, but it never had any issues passing even before I made the changes for DAFFODIL-2262 and I'm not sure what is missing from AD000 that is causing it to not trigger this error.

> unparse array/optional with occursCountKind 'expression' evaluating to 1 or more, doesn't unparse
> -------------------------------------------------------------------------------------------------
>
>                 Key: DAFFODIL-2260
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2260
>             Project: Daffodil
>          Issue Type: Bug
>          Components: Back End
>    Affects Versions: 2.4.0
>            Reporter: Mike Beckerle
>            Assignee: Josh Adams
>            Priority: Major
>             Fix For: 3.0.0
>
>
>  
> Suppose you have an array or optional element with dfdl:occursCountKind="expression".
> Suppose when unparsing, that expression evaluates to 1.
> Suppose the element is complex type.
> Suppose its entire contents can be filled in via dfdl:outputValueCalc.
> In this case, it should unparse 1 occurrence, and when unparsing, the outputValueCalc should be evaluated to fill in the contents of child elements.
> Then it should successfully unparse.
> Unfortunately, right now, the unparser sees no incoming events that match the element, and does not unparse anything.
> Note that in the case where I discovered this bug, the entire array with OCK 'expression' is inside a hidden group, so there will *never* be any infoset events corresponding to it. 
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)