Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Sun, 10 Dec 2017 21:44:00 +0000 (UTC)
From: "Ate Douma (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: <JIRA.12351955.1159431148000.427038.1512942240073@Atlassian.JIRA>
In-Reply-To: <JIRA.12351955.1159431148000@Atlassian.JIRA>
References: <JIRA.12351955.1159431148000@Atlassian.JIRA> <JIRA.12351955.1159431148000@jira-lw-us.apache.org>
Subject: [jira] [Closed] (SCXML-22) The engine must report error/warning
 when invalid events are triggered
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sun, 10 Dec 2017 21:44:11 -0000


     [ https://issues.apache.org/jira/browse/SCXML-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ate Douma closed SCXML-22.
--------------------------
       Resolution: Invalid
    Fix Version/s:     (was: 2.0)

> The engine must report error/warning when invalid events are triggered
> ----------------------------------------------------------------------
>
>                 Key: SCXML-22
>                 URL: https://issues.apache.org/jira/browse/SCXML-22
>             Project: Commons SCXML
>          Issue Type: Improvement
>    Affects Versions: 0.5
>         Environment: Win XP Professional, jdk 1.4.02
>            Reporter: Raj Rao
>
> The semantics must report an error/warning/notification when an invalid event is triggered, instead of silently discarding it. An invalid event is one that is not specified for the current state.
> Here's an excerpt of a converstaion, where the suggested workaround was not applicable. This requirement is crucial for me.
> --
> Raj
> --------------------------------------------------------------------------------------------------------------------------------------
> > Hello,
> >
> > I tried sending an invalid event to the state machine
> > and didn't see any error being reported. By invalid I
> > mean this event was not expected in the current state.
> >
> > Does the SCXMLSemanticsImpl report an error (via the
> > the ErrorReporter) when such an event is silently
> > discarded?
> >
> <snip/>
> No, because the semantics treat it as simply an inconsequential
> trigger (causing no change to the state machine), rather than an
> error.
> One of the ways you could track this is to register a SCXMLListener on
> the executor and track onTransition() callbacks (if you get none, the
> trigger is "invalid" -- per your definition above).
> -Rahul


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)