[
https://issues.apache.org/jira/browse/SCXML-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13839024#comment-13839024
]
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. :-)
Regards,
Woonsan
> Correct error/warning messages in SCXML reading to be up-to-date
> ----------------------------------------------------------------
>
> Key: SCXML-177
> URL: https://issues.apache.org/jira/browse/SCXML-177
> 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
> org.apache.commons.scxml2.io.ModelUpdater.logAndThrowModelError(ModelUpdater.java:297)
> It should inform of 'initial', not 'initialstate' and check if it is not set.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
