commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rahul Akolkar (JIRA)" <j...@apache.org>
Subject [jira] Updated: (SCXML-22) The engine must report error/warning when invalid events are triggered
Date Mon, 02 Oct 2006 15:32:21 GMT
     [ http://issues.apache.org/jira/browse/SCXML-22?page=all ]

Rahul Akolkar updated SCXML-22:
-------------------------------

    Fix Version/s: 0.6

Related discussion thread:

http://www.nabble.com/-SCXML---error-reporting-on-invalid-events-tf2343519.html


> The engine must report error/warning when invalid events are triggered
> ----------------------------------------------------------------------
>
>                 Key: SCXML-22
>                 URL: http://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
>             Fix For: 0.6
>
>
> 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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message