commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Woonsan Ko (JIRA)" <>
Subject [jira] [Commented] (SCXML-177) Correct error/warning messages in SCXML reading to be up-to-date
Date Wed, 04 Dec 2013 15:59:35 GMT


Woonsan Ko commented on SCXML-177:

Hi Ate,

The suggested operations for strict/lenient and silent were mainly for SCXMLReader. The options
in the context of SCXML reading are not really related to the JEXLEngine options which should
play a role in the context of SCXML execution.
With this issue, I think we'd better focus on strict/lenient and silent options in the SCXMLReader
context in order to deal with unexpected / unknown / invalid elements in SCXML model.
As you're already aware of it, JexlEvaluator allows to override #createJexlEngine() to give
additional options.

Regarding the default options of JEXL Engine we might have to take in SCXML, I guess it is
better to use JEXL Engine without any specific options as we do now. Then it means we're using
the default options of JEXL engine as provided, which seems natural to me for most JEXL script
users, IMHO.
Anyway, this JEXL default options issue can be dealt with a separate issue. :-)



> 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