Re: SCXML2 Serialization

Hi Francis, Thanks for the example test code, it helped me detect a bug in the state machine running status management which I already fixed, see [1]. Can you test and verify this now works for you? (note: you'll have to use SCXML trunk). I've one more comment inline below. Regards, Ate [1]

SCXML2 Serialization

Hi Ate It's ok : Loading simple1 Deserialize.. After creation [startIngTrs.processMsg is running : true message:message2 serialize.. Process finished with exit code 0 Thanks Regards, Francis. On Fri, Apr 18, 2014 at 2:12 PM, Ate Douma a...@douma.nu wrote: Hi Francis, Thanks for the example

Re: SCXML2 Serialization

Hi Francis, On 17-04-14 07:48, ten...@free.fr wrote: Hi Ate, I put Simple1.java and Simple1.xml here : http://tendaf.free.fr/ I'll try to make some time tomorrow to test drive your example. Regards, Ate When I run the program (second time) the fsm is frozen : First time : After creation

SCXML2 Serialization

Hi all, I would like to know the best practice to serialize/deserialize SCXML fsm. I do this during the creation of the SCXML executor, scInstace is the serialized context: ListCustomAction customActions = new ArrayListCustomAction(); CustomAction ca =

Re: SCXML2 Serialization

Hi Francis, I think the best practices are to serialize either o.a.c.s.SCXMLExecutor [1] or o.a.c.s.model.SCXML instances. Both cases are well-maintained in test code. [2] In your case, you can probably (de)serialize SCXMLExecutor instance directly to store/load the execution context. Also, as

Re: SCXML2 Serialization

Hi Francis, There are a few things not right or needed in your approach below. I've provided comments inline. On 16-04-14 15:07, ten...@free.fr wrote: Hi all, I would like to know the best practice to serialize/deserialize SCXML fsm. I do this during the creation of the SCXML executor,

Re: SCXML2 Serialization

Hi Woonsan, On 16-04-14 15:49, Woonsan Ko wrote: Hi Francis, I think the best practices are to serialize either o.a.c.s.SCXMLExecutor [1] or o.a.c.s.model.SCXML instances. Both cases are well-maintained in test code. [2] Actually, since the last milestone SCXMLExecutor no longer is

Re: SCXML2 Serialization

On Wednesday, April 16, 2014 9:57 AM, Ate Douma a...@douma.nu wrote: Hi Woonsan, On 16-04-14 15:49, Woonsan Ko wrote: Hi Francis, I think the best practices are to serialize either o.a.c.s.SCXMLExecutor [1] or o.a.c.s.model.SCXML instances. Both cases are well-maintained in test code.

RE: SCXML2 Serialization

Thanks for your reply Ate. I want to serialize/deserialize a SCXML 'session' for this use case : Into a transactional server, a request is processed by a thread. An ID is retrieved from the message, with this ID the server loads a context (from a redis store) and instantiates a new 'Executor'

SCXML2 Serialization

Hi Ate, I put Simple1.java and Simple1.xml here : http://tendaf.free.fr/ When I run the program (second time) the fsm is frozen : First time : After creation [startIngTrs.processMsg is running : true message:message1 serialize.. Process finished with exit code 0 Second time : Loading simple1