commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ate Douma (JIRA)" <>
Subject [jira] [Commented] (SCXML-177) Correct error/warning messages in SCXML reading to be up-to-date
Date Thu, 05 Dec 2013 13:06:37 GMT


Ate Douma commented on SCXML-177:

Hi Woonsan,

Nice work!
I agree managing the JEXL Engine options for silent/strict are a separate issue, and maybe
we should stick to the current 'lenient' configurations by default for easier backwards compatibility.

I like to provide an easier way to configure these properties on the JEXL Engine though, currently
you have to extend the JEXLEvaluator for this which is less convenient.
It is trivial to improve though and I've created separate issue SCXML-183 for that.

With these changes as well as SCXML-180 the error control of SCXML has been greatly improved!

> Correct error/warning messages in SCXML reading to be up-to-date
> ----------------------------------------------------------------
>                 Key: SCXML-177
>                 URL:
>             Project: Commons SCXML
>          Issue Type: Bug
>            Reporter: Woonsan Ko
>            Assignee: Woonsan Ko
>            Priority: Trivial
>             Fix For: 2.0
> Some error/warning logs are outdated against the newest spec.
> For example,
> org.apache.commons.scxml2.model.ModelException: No SCXML child state with ID "null" found;
illegal initialstate for SCXML document
> 	at
> It should inform of 'initial', not 'initialstate' and check if it is not set.

This message was sent by Atlassian JIRA

View raw message