You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "Rahul Akolkar (JIRA)" <ji...@apache.org> on 2006/09/28 17:49:51 UTC
[jira] Commented: (SCXML-22) The engine must report error/warning
when invalid events are triggered
[ http://issues.apache.org/jira/browse/SCXML-22?page=comments#action_12438470 ]
Rahul Akolkar commented on SCXML-22:
------------------------------------
There is no such requirement for an SCXML engine, but its useful feedback I agree. Two questions:
(a) While the workaround is clearly just that, can you elaborate why its not applicable for you?
(b) Generally speaking, this is application specific behavior as far as Commons SCXML is concerned, so we can't hardcode an error/warning (or anything else for that matter). What would be a good way to receive that feedback, for your usecase?
> 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
>
> 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