[
https://issues.apache.org/jira/browse/DAFFODIL-2594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17605377#comment-17605377
]
Mike Beckerle commented on DAFFODIL-2594:
-----------------------------------------
related issue I believe:
I get compilation errors about expressions where the reported file and line
number are nowhere near the expression at fault, but the nearest enclosing
element of the expression is the one that is identified as the problem (with
line number).
E.g., The problem is in an expression that is inside a group which is inside
the payload element, but that group is defined in a different file than this
payload element.
{code:java}
[error] Schema Definition Error: No element corresponding to step
{}milstd2045_application_header found. Possibilities for this step include:
{}message, {}binary_file.
Schema context: payload Location line 70 column 8 in
file:/home/mbeckerle/Documents/dataiti/owlsvcs/services/PMMC-HTN/pmmc-htn-schemas/src/main/resources/com/owlcyberdefense/vmf-multi/xsd/vmf-message-with-header.dfdl.xsd
{code}
> Diagnostic message has wrong line number for setVariable with an expression
> error
> ---------------------------------------------------------------------------------
>
> Key: DAFFODIL-2594
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2594
> Project: Daffodil
> Issue Type: Bug
> Components: Diagnostics
> Affects Versions: 3.1.0
> Reporter: Mike Beckerle
> Priority: Minor
>
> See test_setVariable_neg_line_info_01
> The line number given is the xs:schema element, which is useless. It should
> be the line number of the setVariable statement.
> A similar issue almost certainly will occur for dfdl:newVariableInstance if
> the default value expression gets a runtime error as well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
