You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "Olabusayo Kilo (Jira)" <ji...@apache.org> on 2025/08/06 17:43:00 UTC

[jira] [Updated] (DAFFODIL-3006) Unexpected SDE: Failed to start infoset simple element: Expression Evaluation Error: Element does not have a value.

     [ https://issues.apache.org/jira/browse/DAFFODIL-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Olabusayo Kilo updated DAFFODIL-3006:
-------------------------------------
    Fix Version/s:     (was: 4.0.0)

> Unexpected SDE: Failed to start infoset simple element: Expression Evaluation Error: Element does not have a value. 
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: DAFFODIL-3006
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-3006
>             Project: Daffodil
>          Issue Type: Bug
>          Components: Back End
>    Affects Versions: 3.11.0
>            Reporter: Steve Lawrence
>            Assignee: Steve Lawrence
>            Priority: Major
>
> In specific cases, such a  combination of a schema without points of uncertainties, use of JDOM or SAX infoset outputters, and invalid data leading to a parse error, it is possible for Daffodil to attempt to project an infoset element that does not have value into the target infoset. In this situation, this can lead to an SDE like this:
> {code}
> Schema Definition Error: Failed to start infoset simple element: Expression Evaluation Error: Element does not have a value.
> {code}
> This SDE will stop all processing and prevent backtracking that would otherwise occur to provide additional context of the failure, potentially leading to missing expected diagnostics. Note that the core diagnostic will still exist and the parse result will still be an error, the diagnostics just might not contain as much information as you would otherwise expect.
> Note that this SDE is really just the most visible symptom--the core issue is that Daffodil should not walk into elements that failed to parse and try to project them to an infoset.



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