Reporter: Ingmar Kliche
The current implementation of SimpleSCXMLInvoker assumes that only external
events, handled by parentEvents(), may cause the child state machine to go move
a final state. But in case where the invoked state machine moves to a final
state directly (while
The current implementation of SimpleSCXMLInvoker assumes that only external
events, handled by parentEvents(), may cause the child state machine to
go move a final state. I had a case where the invoked state machine went to
a final state directly while executing the initial state, something like:
Rahul,
I would like to inject events with XML payload into the SCXML engine.
Currently we have to convert XML represented messages received from external
components into a hashmap object to fire the event into the engine. But this
does not allow to include XML attributes easily. Suppose we have
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
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
!--
Rahul,
within a transition (which is gets eventdata from outside) I'd like to
forward some pieces of the eventdata structure using a send with namelist:
transition event=change
if cond = _eventdata.eventSource == 'x'
send targettype=GUI target='y' event=change namelist=
Project: Commons SCXML
Issue Type: Bug
Affects Versions: 0.6
Reporter: Ingmar Kliche
Priority: Minor
Events which are sent to the current scxml session using the send tag (i.e.
target = empty) may contain payload specified by the namelist attribute. This
payload
Rahul,
the send tag may be used to send events to external systems or to
raise (external) events within the current SCXML session. I'm trying
to structure my SCXML document into logically and hierarchically separated
state machines (within one document, i.e. without invoking an external SCXML
I noticed that commons-scxml executes multiple transitions on one event as
soon as multiple transitions (i.e. multiple transitions exist for one event)
match. The SCXML spec instead says that only one transition has to be taken
(the first in document order) as long as it is not a parallel
Rahul,
nice to see that you are already working on the Feb '07 WD support. We
really appreciate this! Thank you for your effort!
How far are these changes? Do you plan to build a new release (e.g. 0.7) or
do I need to check out from SVN to get the Feb '07 support? Currently I use
rel v0.6 and
10 matches
Mail list logo
