[
https://issues.apache.org/jira/browse/DAFFODIL-2895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Lawrence updated DAFFODIL-2895:
-------------------------------------
Component/s: Back End
Affects Version/s: 3.7.0
Description: The finally block for the ElementCombinator parser calls
parseEnd which does restriction validation. But if an exception was thrown then
we do not have a value to validate, which creates an "Element does not have a
value" exception and hides the underlying exception. We should only perform
validation if the parser actually succeeds, so this logic needs to be moved out
of the finally block.
Issue Type: Bug (was: Improvement)
Summary: Runtime SDE in ElementCombinator parser with validation
causes "Expression Evaluation Error: Element does not have a value" (was:
Runtime SDE in ElementCombinator parser with validation causes Expression
Evaluation Error: Element does not have a value)
> Runtime SDE in ElementCombinator parser with validation causes "Expression
> Evaluation Error: Element does not have a value"
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: DAFFODIL-2895
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2895
> Project: Daffodil
> Issue Type: Bug
> Components: Back End
> Affects Versions: 3.7.0
> Reporter: Steve Lawrence
> Priority: Major
>
> The finally block for the ElementCombinator parser calls parseEnd which does
> restriction validation. But if an exception was thrown then we do not have a
> value to validate, which creates an "Element does not have a value" exception
> and hides the underlying exception. We should only perform validation if the
> parser actually succeeds, so this logic needs to be moved out of the finally
> block.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
