Re: [scxml] stop and resume by serializing the executor does not work

On Fri, Jul 2, 2010 at 7:04 PM, RT aara...@gmail.com wrote: I tried your suggestion -  executor.getCurrentStatus().getStates() - in a few places and I noticed something interesting. snip/ OK, reading the content below, this isn't a serialization round trip issue then (that would've been

Re: [scxml] stop and resume by serializing the executor does not work

On Thu, Jul 1, 2010 at 8:56 PM, RT aara...@gmail.com wrote: My scxml is defined like this:                       state id=stateA                                onentry                                        log expr='Inside stateA'/                                /onentry                    

Re: [scxml] stop and resume by serializing the executor does not work

I tried your suggestion - executor.getCurrentStatus().getStates() - in a few places and I noticed something interesting. So, using the context explained in my prev email, (without the serialization/deserialization): 1. state machine starts 2. onEntry() gets called for stateA - here I call the

[scxml] stop and resume by serializing the executor does not work

My scxml is defined like this: state id=stateA onentry log expr='Inside stateA'/ /onentry onexit