[
https://issues.apache.org/jira/browse/DAFFODIL-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Lawrence resolved DAFFODIL-3006.
--------------------------------------
Resolution: Fixed
Fixed in commit 1e26e299965e56774a8e1c38ef5cbd5b4675c250
> 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
> Fix For: 4.0.0
>
>
> 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)
