Return-Path: X-Original-To: apmail-commons-issues-archive@minotaur.apache.org Delivered-To: apmail-commons-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4D68110FEF for ; Thu, 5 Dec 2013 13:07:32 +0000 (UTC) Received: (qmail 57193 invoked by uid 500); 5 Dec 2013 13:06:56 -0000 Delivered-To: apmail-commons-issues-archive@commons.apache.org Received: (qmail 57067 invoked by uid 500); 5 Dec 2013 13:06:43 -0000 Mailing-List: contact issues-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: issues@commons.apache.org Delivered-To: mailing list issues@commons.apache.org Received: (qmail 56968 invoked by uid 99); 5 Dec 2013 13:06:37 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Dec 2013 13:06:37 +0000 Date: Thu, 5 Dec 2013 13:06:37 +0000 (UTC) From: "Ate Douma (JIRA)" To: issues@commons.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (SCXML-177) Correct error/warning messages in SCXML reading to be up-to-date MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/SCXML-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13840061#comment-13840061 ] 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: 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)