[
https://issues.apache.org/jira/browse/SCXML-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13837820#comment-13837820
]
Rahul Akolkar commented on SCXML-177:
-------------------------------------
+1 to having a strict and lenient configuration for the SCXMLReader.
I suggest not changing behavior to throw a ModelException in all cases. Besides
the compatibility aspect of doing this, leniency is appropriate or even desired
in certain usecases involving compound namespace documents where not all parts
of the document may relate to (or be generated for) the purposes of the
document controller or state machine.
> 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)
