Hi Rahul,
there must be a difference between the nightlies of 20060324 and 20060325.
Since nightly 20060325 I got the error messages. It must have to do
something with the "send" tag at "onentry". When I use the "send" tag I get
the errors (right after calling "go" of SCXMLExecutor). Here's a sample of
mine:
<?xml version="1.0" encoding="UTF-8"?>
<scxml xmlns="http://www.w3.org/2005/07/SCXML";
version="1.0"
initialstate="state1">
<state id="state1">
<onentry>
<var name="aValue" expr="1"/>
<send namelist="aValue"/>
</onentry>
<transition event="event2" target="state2"/>
<transition event="event3" target="state3"/>
<transition event="event4" target="state4"/>
</state>
<state id="state2">
<onentry>
<var name="aValue" expr="2"/>
<send namelist="aValue"/>
</onentry>
<transition event="event1" target="state1"/>
<transition event="event3" target="state3"/>
<transition event="event4" target="state4"/>
</state>
<state id="state3">
<onentry>
<var name="aValue" expr="3"/>
<send namelist="aValue"/>
</onentry>
<transition event="event1" target="state1"/>
<transition event="event2" target="state2"/>
<transition event="event4" target="state4"/>
</state>
<state id="state4">
<onentry>
<var name="aValue" expr="4"/>
<send namelist="aValue"/>
</onentry>
<transition event="event1" target="state1"/>
<transition event="event2" target="state2"/>
<transition event="event3" target="state3"/>
</state>
</scxml>
And if you try the next sample you'll get an endless loop
<?xml version="1.0" encoding="UTF-8"?>
<scxml xmlns="http://www.w3.org/2005/07/SCXML";
version="1.0"
initialstate="state1">
<state id="state1">
<onentry>
<var name="aValue" expr="1"/>
<send namelist="aValue"/>
</onentry>
<transition event="event2" target="state2"/>
</state>
<state id="state2">
<onentry>
<var name="aValue" expr="2"/>
<send namelist="aValue"/>
</onentry>
<transition event="event1" target="state1"/>
</state>
</scxml>
Up to nightly 20060324 it worked fine and I could use an event dispatcher
to get the information from "send" tag.
Regards,
Heiko
On 27.03.2006 20:50:21 Rahul Akolkar wrote:
>On 3/27/06, [EMAIL PROTECTED]
><[EMAIL PROTECTED]> wrote:
>>
>> Hi,
>>
>> I've downloaded the latest version of SCXML and suddenly I've got some
>> errors. I defined some transitions to a state which will be triggered by
>> events. But when the state machine is being loaded or when the executor
>> starts with "go" there are warnings like the following:
>>
>> 2006-03-27 16:41:30,511 WARN - 27.03.2006 16:41:30
>> org.apache.commons.scxml.env.SimpleErrorReporter onErrorWARNUNG:
>> NON_DETERMINISTIC (Multiple conflicting transitions enabled.):
[transition
>> (event = ...
>>
>> 2006-03-27 16:41:30,542 WARN - 27.03.2006 16:41:30
>> org.apache.commons.scxml.env.SimpleErrorReporter onError
>> WARNUNG: ILLEGAL_CONFIG (Multiple top-level OR states active!): <SCXML>
: [
>>
><snip/>
>
>As a bit of a window into what this means, the only case where SCXML
>semantics allow multiple (simple a.k.a leaf) states to be "active" at
>the same time is if they are each part of a (different) region within
>a <parallel>. So, for the pruned document below:
>
><scxml initialstate="alpha" ...>
>
> <state id="alpha" ... />
>
> <state id="beta" ... />
>
> <state id="gamma">
> <parallel id="p1">
>
> <!-- s1 and s2 are "regions" -->
> <state id="s1">
> <state id="s11" ... />
> </state>
>
> <state id="s2">
> <state id="s21" ... />
> </state>
>
> </parallel>
> </state>
>
></scxml>
>
>it is legal for the state machine to have states "s11" and "s21"
>active at the same time (note use of <parallel>), but it is illegal to
>have states "alpha" and "beta" active at the same time. The above
>error message states that the particular SCXML document being used was
>authored such that a scenario similar to the latter one has come about
>during execution.
>
>Incidently, I mentioned the "default" policy for handling
>non-determinism that is used by Commons SCXML in an unrelated thread
>on commons-dev. I will cross-post that here as a hyperlink [1], since
>its probably relevant to the discussion (See paragraph beginning with
>"As a concrete example" roughly halfway down the post).
>
>
>> The state definition looks like this:
>>
>> ...
>> <state id="mystate1">
>> <onentry>
>> ...
>> </onentry>
>> <transition event="event2" target="mystate2"/>
>> <transition event="event3" target="mystate3"/>
>> ...
>> <state id="mystate2">
>> ...
>>
>> Did I make something wrong (last week it worked fine)?
>>
><snap/>
>
>I don't see anything out of place in this snippet. Can you please post
>the smallest possible complete SCXML document that illustrates the
>problem? I might then be of more help. ATM, I'm also unsure what
>change over the last week could have caused a regression. The
>nightlies [2] seem to be still cranking, if we indeed discover an
>issue we should wire up your test case to the nightlies as well.
>
>Thanks,
>-Rahul
>
>[1]
http://marc.theaimsgroup.com/?l=jakarta-commons-dev&m=114332465230997&w=2
>[2] http://cvs.apache.org/builds/jakarta-commons/nightly/commons-scxml/
>
>
>> Regards,
>>
>> Heiko
>>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
