Wild card event name handling on transitions is not in line with W3C WD
-----------------------------------------------------------------------

                 Key: SCXML-53
                 URL: https://issues.apache.org/jira/browse/SCXML-53
             Project: Commons SCXML
          Issue Type: Bug
    Affects Versions: 0.6
            Reporter: Ingmar Kliche
            Priority: Minor


The current W3C SCXML WD [1] states for wild card event names on transitions:

"Events have names which are matched against the "event" attribute of 
transitions. These names are strings consisting of alphanumeric characters plus 
the character '.' which is used to segment names into tokens. The "event" 
attribute of a transition may end with the wildcard '.*', which will match zero 
or more tokens at the end of the processed event's name. Thus a transition with 
an "event" attribute of 'error.*' will match 'error', 'error.send', 
'error.send.failed', etc. Furthermore, a transition with an "event" attribute 
consisting solely of '*' will match any event."

>From my understanding therefore the following example should work:

<?xml version="1.0"?>
<scxml
  xmlns="http://www.w3.org/2005/07/scxml";
  version="1.0" 
  initialstate="s1"
  id="demo">

        <state id="s1">
                <onentry>
                    <send event="success.start"/>
                </onentry>
                <transition event="success.*" target="s2"/>
        </state>
        <state id="s2">
        </state>
</scxml>

But this transition does not match for the current commons-SCXML implementation 
(SNAPSHOT-0.7). Commons-SCXML does not expect the ".*", instead the following 
works: <transition event="succcess" .../>. 

Also the <transition event="*"/> does not work, even though I don't know if 
this is really useful because it would match "every" internal .entry and .exit 
event. 

Regards,
Ingmar

[1] http://www.w3.org/TR/2007/WD-scxml-20070221/#events

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to