Re: [scxml] bug with script in combination of a chain of transitions
Hi Rinke, Did you run with commons-scxml2-2.0-SNAPSHOT? I've tried to run the following similar to yours on latest revision, but the result seems different from what you're seeing: ?xml version=1.0 ? scxml xmlns=http://www.w3.org/2005/07/scxml; version=1.0 datamodel=jexl initial=test1 state id=test1 initial=test1.1 state id=test1.1 onentry log expr='logging in test1.1' / /onentry transition event=test1.1.positive target=test1.2/ /state state id=test1.2 onentry log expr='logging in test1.2' / /onentry transition event=test1.2.positive target=test1.3/ /state state id=test1.3 onentry log expr='logging in test1.3' / /onentry /state /state /scxml I removed the custom action tags and replaced the script tag with simple log tags. And I see the following when I tested it with the stanadlone tool [1]: $ ./scxml.sh test.scxml ?xml version=1.0 encoding=UTF-8?scxml xmlns=http://www.w3.org/2005/07/scxml; xmlns:cs=http://commons.apache.org/scxml; version=1.0 initial=test1 datamodel=jexl 8 8 /scxml May 05, 2015 11:44:51 PM org.apache.commons.scxml2.env.SimpleSCXMLListener onEntry INFO: enter /test1 May 05, 2015 11:44:51 PM org.apache.commons.scxml2.model.Log execute INFO: null: logging in test1.1 May 05, 2015 11:44:51 PM org.apache.commons.scxml2.env.SimpleSCXMLListener onEntry INFO: enter /test1/test1.1 test1.1.positive May 05, 2015 11:45:16 PM org.apache.commons.scxml2.env.SimpleSCXMLListener onExit INFO: exit /test1/test1.1 May 05, 2015 11:45:16 PM org.apache.commons.scxml2.env.SimpleSCXMLListener onTransition INFO: transition (event = test1.1.positive, cond = null, from = /test1/test1.1, to = /test1/test1.2) May 05, 2015 11:45:16 PM org.apache.commons.scxml2.model.Log execute INFO: null: logging in test1.2 May 05, 2015 11:45:16 PM org.apache.commons.scxml2.env.SimpleSCXMLListener onEntry INFO: enter /test1/test1.2 test1.2.positive May 05, 2015 11:45:47 PM org.apache.commons.scxml2.env.SimpleSCXMLListener onExit INFO: exit /test1/test1.2 May 05, 2015 11:45:47 PM org.apache.commons.scxml2.env.SimpleSCXMLListener onTransition INFO: transition (event = test1.2.positive, cond = null, from = /test1/test1.2, to = /test1/test1.3) May 05, 2015 11:45:47 PM org.apache.commons.scxml2.model.Log execute INFO: null: logging in test1.3 May 05, 2015 11:45:47 PM org.apache.commons.scxml2.env.SimpleSCXMLListener onEntry INFO: enter /test1/test1.3 (I typed 'test1.1.positive' and 'test1.2.positive' to trigger those events manually.) So, the execution order is as follows: 1. enter into test1 state 2. execute actions in onentry of test1.1 state 3. enter into test1.1 state and wait 4. 'test1.1.positive' event triggered manually 5. exit from test1.1 state 6. transition from test1.1 to test 1.2 state 7. execute actions in onentry of test1.2 state 8. enter into test1.2 state 9. 'test1.2.positive' event triggered manually 10. exit from test1.2 state 11. transition from test1.2 to test1.3 state 12. execute actions in onentry of test1.3 state 13. enter into test1.3 state I don't think script action would be different from log action in execution ordering, so I think you're seeing a different result on your end for some reason. Maybe you can try to find what the difference comes from? Regards, Woonsan [1] http://commons.apache.org/proper/commons-scxml/guide/testing-standalone.html On Fri, 4/17/15, R.C. Hoekstra r.c.hoeks...@erasmusmc.nl wrote: Subject: [scxml] bug with script in combination of a chain of transitions To: user@commons.apache.org user@commons.apache.org Date: Friday, April 17, 2015, 4:12 AM Dear people at scxml, I found a bug in the scxml commons project. Consider this scxml file: state id=test1 initial=test1.1 state id=test1.1 onentry ntd:test id=test1.1 isIn=test1.1 / script agent.storeInMemory(test1.1); /script /onentry transition event=test1.1.positive target=test1.2/ /state state id=test1.2 onentry ntd:test id=test1.2 isIn=test1.1 memory=true / /onentry transition event=test1.2.positive target=test1.3/ /state state id=test1.3/ /state There is a custom tag, which simply tests if the state machine is at present in the state specified in the isIn attribute. If it is, it sends an event id.positive, else it sends id.negative. The purpose of this is that we needed a memory: a test that the state machine has at any moment been in a certain state. That is done via the script tag: via the agent.storeInMemory(test1.1) call, the test1.1 state is stored in the memory of the agent, and ntd:test tag considers this memory if the memory=true attribute is specified. As the state test1.1 is stored in memory while
RE: [configuration] Apache Commons Configuration Version 2
Oliver, I guess I could build it from source and store it in our local Nexus until a release version is built. Ron DiFrango -Original Message- From: DiFrango, Ronald (CONT) [mailto:ronald.difra...@capitalone.com] Sent: Tuesday, May 05, 2015 4:23 PM To: Commons Users List Subject: RE: [configuration] Apache Commons Configuration Version 2 Oliver, I figured it would be something like that and that's understandable as is the time-table. We definitely like the feature set of 2.x as it supports many of the uses cases more naturally than 1.x so would like to move forward with it. But I can't unless it's in maven central. Thanks, Ron -Original Message- From: Oliver Heger [mailto:oliver.he...@oliver-heger.de] Sent: Tuesday, May 05, 2015 4:20 PM To: Commons Users List Subject: Re: [configuration] Apache Commons Configuration Version 2 Hi Ron, Am 05.05.2015 um 22:09 schrieb DiFrango, Ronald (CONT): All, Is Apache commons configuration in maven central or some other repo? I'm using Gradle and pointing to an internal Nexus repo that is a proxy for Maven central and I can't resolve it as follows: compile group: 'org.apache.commons', name: 'commons-configuration2', version: '2.0-alpha2' because it is only an alpha release, this version has not been deployed to a public Maven repository. We did this by intension to avoid potential jar hell if there are still binary incompatible changes before the final release. I am working to get the final version 2.0 out, but unfortunately my time is currently pretty limited. So I cannot predict a release schedule. Oliver Thanks, Ron The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer. - To unsubscribe, e-mail: user-unsubscr...@commons.apache.org For additional commands, e-mail: user-h...@commons.apache.org The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer. - To unsubscribe, e-mail: user-unsubscr...@commons.apache.org For additional commands, e-mail: user-h...@commons.apache.org The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer. - To unsubscribe, e-mail: user-unsubscr...@commons.apache.org For additional commands, e-mail: user-h...@commons.apache.org
[configuration] Apache Commons Configuration Version 2
All, Is Apache commons configuration in maven central or some other repo? I'm using Gradle and pointing to an internal Nexus repo that is a proxy for Maven central and I can't resolve it as follows: compile group: 'org.apache.commons', name: 'commons-configuration2', version: '2.0-alpha2' Thanks, Ron The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.
Re: [configuration] Apache Commons Configuration Version 2
Hi Ron, Am 05.05.2015 um 22:09 schrieb DiFrango, Ronald (CONT): All, Is Apache commons configuration in maven central or some other repo? I'm using Gradle and pointing to an internal Nexus repo that is a proxy for Maven central and I can't resolve it as follows: compile group: 'org.apache.commons', name: 'commons-configuration2', version: '2.0-alpha2' because it is only an alpha release, this version has not been deployed to a public Maven repository. We did this by intension to avoid potential jar hell if there are still binary incompatible changes before the final release. I am working to get the final version 2.0 out, but unfortunately my time is currently pretty limited. So I cannot predict a release schedule. Oliver Thanks, Ron The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer. - To unsubscribe, e-mail: user-unsubscr...@commons.apache.org For additional commands, e-mail: user-h...@commons.apache.org
RE: [configuration] Apache Commons Configuration Version 2
Oliver, I figured it would be something like that and that's understandable as is the time-table. We definitely like the feature set of 2.x as it supports many of the uses cases more naturally than 1.x so would like to move forward with it. But I can't unless it's in maven central. Thanks, Ron -Original Message- From: Oliver Heger [mailto:oliver.he...@oliver-heger.de] Sent: Tuesday, May 05, 2015 4:20 PM To: Commons Users List Subject: Re: [configuration] Apache Commons Configuration Version 2 Hi Ron, Am 05.05.2015 um 22:09 schrieb DiFrango, Ronald (CONT): All, Is Apache commons configuration in maven central or some other repo? I'm using Gradle and pointing to an internal Nexus repo that is a proxy for Maven central and I can't resolve it as follows: compile group: 'org.apache.commons', name: 'commons-configuration2', version: '2.0-alpha2' because it is only an alpha release, this version has not been deployed to a public Maven repository. We did this by intension to avoid potential jar hell if there are still binary incompatible changes before the final release. I am working to get the final version 2.0 out, but unfortunately my time is currently pretty limited. So I cannot predict a release schedule. Oliver Thanks, Ron The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer. - To unsubscribe, e-mail: user-unsubscr...@commons.apache.org For additional commands, e-mail: user-h...@commons.apache.org The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer. - To unsubscribe, e-mail: user-unsubscr...@commons.apache.org For additional commands, e-mail: user-h...@commons.apache.org
