You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "Rick (Jira)" <ji...@apache.org> on 2020/09/03 15:38:00 UTC
[jira] [Issue Comment Deleted] (DAFFODIL-1043) Bad diagnostic
message: The type Complex cannot be converted to ....
[ https://issues.apache.org/jira/browse/DAFFODIL-1043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick updated DAFFODIL-1043:
---------------------------
Comment: was deleted
(was: With regard to test_checkConstraintsComplexTypeFails
The relevant code is in InfosetImpl.scala LN 166
In this case the exposed object is node as an instance of DINode
which does not appear to have access to the expression context object.
)
> Bad diagnostic message: The type Complex cannot be converted to ....
> --------------------------------------------------------------------
>
> Key: DAFFODIL-1043
> URL: https://issues.apache.org/jira/browse/DAFFODIL-1043
> Project: Daffodil
> Issue Type: Bug
> Components: Back End, Diagnostics, Front End, Usability
> Affects Versions: s15
> Reporter: Mike Beckerle
> Assignee: Rick
> Priority: Minor
> Labels: beginner
>
> The type Complex cannot be converted to .....
> This schema definition error is produced in situations where one has a complex element type, but you are using it in an expression that requires a simple type.
> The message needs to provide more info. E.g.,
> test_checkConstraintsComplexTypeFails has an expression containing dfdl:checkConstraints(.) but on a complex type. The message doesn't contain the expression text anywhere.
> test_assertFailShowsValue2 has an assertion which tries to evaluate the expression "." on a complex type. Again no mention of the expression, or it appearing in an assertion test.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)