[
https://issues.apache.org/jira/browse/SCXML-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13837770#comment-13837770
]
Woonsan Ko commented on SCXML-177:
----------------------------------
I couldn't find any statement specifying that. And I agree that it should've
been logged as ERROR level.
SCXMLReader invokes #reportIgnoredElement() and it leaves a warning log and
invokes XMLReporter#report() in the end.
The current warnings in #reportIgnoredElement() are logged when there are
unexpected or invalid elements inside an SCXML element (e.g, no 'data' element
inside 'datamodel'). So, I think this warning should be logged as ERROR level.
In that way, users can be informed of the error more clearly.
> 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)
