You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "Steve Lawrence (Jira)" <ji...@apache.org> on 2024/12/16 13:43:00 UTC

[jira] [Commented] (DAFFODIL-2962) Complex nillable leads to Expression Evaluation Error: Element does not have a value.

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

Steve Lawrence commented on DAFFODIL-2962:
------------------------------------------

PR to fix this: https://github.com/apache/daffodil/pull/1392

> Complex nillable leads to Expression Evaluation Error: Element does not have a value.
> -------------------------------------------------------------------------------------
>
>                 Key: DAFFODIL-2962
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2962
>             Project: Daffodil
>          Issue Type: Bug
>          Components: Back End
>    Affects Versions: 3.9.0
>            Reporter: Robert Bathmann
>            Assignee: Steve Lawrence
>            Priority: Major
>         Attachments: noValueTest.tdml
>
>
> Consider the DFDL schema in the attached TDML file. It describes an array of line-delimited elements containing a nillable complex element within a direct dispatch choice. A simple pattern discriminator is placed on the line element.
> This schema works properly for six occurrences of the line element. However, adding a seventh line results in the error: 
> {code:java}
> Schema Definition Error: Failed to start infoset complex element: Expression Evaluation Error: Element does not have a value.{code}
> Removing the discriminator, the dispatch key and branch key, or changing the innermost complex element to nillable="false" allows the larger document to be parsed.
> If additional structures are added within the nillable complex element, this error can be reproduced with a smaller number of line elements. This is not illustrated within the TDML for simplicity.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)