Revision control
++ <?xml version="1.0" encoding="UTF-8"?><!-- test that any attempt to change the value of a system variable causes error.execution to be raised.
++ Event1..4 are there to catch the case where the error event is not raised. In cases where it is, we have
++ to dispose of eventn in the next state, hence the targetless transitions (which simply throw away the event.) --><scxml xmlns="http://www.w3.org/2005/07/scxml" xmlns:conf="http://www.w3.org/2005/scxml-conformance" initial="s0" version="1.0" datamodel="ecmascript" name="machineName">
++
++
++ <state id="s0">
++ <onentry>
++ <assign location="_sessionid" expr="'otherName'"/>
++ <raise event="event1"/>
++ </onentry>
++
++ <transition event="error.execution" target="s1"/>
++ <transition event="*" target="fail"/>
++ </state>
++
++ <state id="s1">
++ <onentry>
++ <assign location="_event" expr="'otherName'"/>
++ <raise event="event2"/>
++ </onentry>
++ <!-- throw out event1 if it's still around -->
++ <transition event="event1"/>
++ <transition event="error.execution" target="s2"/>
++ <!-- event1 would trigger this transition if we didn't drop it. We want this transition to have
++ a very general trigger to catch cases where the wrong error event was raised -->
++ <transition event="*" target="fail"/>
++ </state>
++
++ <state id="s2">
++ <onentry>
++ <assign location="_ioprocessors" expr="'otherName'"/>
++ <raise event="event3"/>
++ </onentry>
++ <transition event="event2"/>
++ <transition event="error.execution" target="s3"/>
++ <transition event="*" target="fail"/>
++ </state>
++
++ <state id="s3">
++ <onentry>
++ <assign location="_name" expr="'otherName'"/>
++ <raise event="event4"/>
++ </onentry>
++ <transition event="event3"/>
++ <transition event="error.execution" target="pass"/>
++ <transition event="*" target="fail"/>
++ </state>
++
++
++ <final id="pass"><onentry><log label="Outcome" expr="'pass'"/></onentry></final>
++ <final id="fail"><onentry><log label="Outcome" expr="'fail'"/></onentry></final>
++
++ </scxml>