Rahul,
thanks for clarification. In this case I consider it to be a feature (which
could indeed be very useful) rather than a bug.
* The Commons SCXML implementation generates a .change event when a
piece of any data model changes (similarly it generates a .entry when
any state is entered
On 6/23/07, Ingmar Kliche [EMAIL PROTECTED] wrote:
snip/
I understand there are some subtleties here, and the above definitely
needs to be better documented. If you want to help, feel free to add
some of your recent experiences and some of the pitfalls to the
Commons SCXML wiki [1] by
Rahul,
I have a strange behavior with one of my samples I'm currently playing with.
I try generate a number of timer events (like a count down) using a variable
in the data model and delayed events:
datamodel
data name=timer expr = '5'/
/datamodel
state id=welcome
onentry
!--
Before we get into the specifics below, some background:
* Event names imply an ontology. So an error.foo event is an
error event, and so is the error.foo.bar event (which, in
addition, is also a type of error.foo event). Therefore, the
following transition ...
transition event=error
