SCXML-tutorial

Contents	Overview	Examples	Editor	Forum

<onexit>

Video version

A wrapper element containing executable content to be executed when the state is exited.

The SCXML processor must execute the handlers of a state in document order when the state is exited. In doing so, it must treat each handler as a separate block of executable content.

<scxml initial="State1" name="Scxml" version="1.0" xmlns="http://www.w3.org/2005/07/scxml">
	<state id="State1">
		<onexit>
			<log expr="Bye from 'State1'!"/>
		</onexit>
		<transition target="Container"/>
	</state>
	<state id="Container" initial="State2">
		<onexit>
			<log expr="Bye from 'Container'!"/>
		</onexit>
		<transition target="End"/>
		<state id="State2">
			<onexit>
				<log expr="Bye from 'State2'!"/>
			</onexit>
			<transition target="State3"/>
		</state>
		<state id="State3">
			<onexit>
				<log expr="Bye from 'State3'!"/>
			</onexit>
		</state>
	</state>
	<final id="End">
		<onexit>
			<log expr="Bye from 'End'!"/>
		</onexit>
	</final>
</scxml>

Output:

[Log] "Bye from 'State1'!"
[Log] "Bye from 'State2'!"
[Log] "Bye from 'State3'!"
[Log] "Bye from 'Container'!"
[Log] "Bye from 'End'!"

W3C IRP tests

1. Test 377

The SCXML processor MUST execute the onexit handlers of a state in document order when the state is exited.

2. Test 378

The SCXML processor MUST treat each <onexit> handler as a separate block of executable content.

TOP	Contents	Overview	Examples	Editor	Forum

This site is open source. Improve this page.