On Wed, Jul 30, 2008 at 3:03 PM, Daniel Schwager
<[EMAIL PROTECTED]> wrote:
> Hi Rahul,
>
> in <parallel> section, a <onentry> element have to work also with
> context variables
> (http://www.w3.org/TR/scxml/#N102F2) - but I got an exception like shown
> below.
>
> If I remove the log-statement in parallel.onentry, the fsm works fine
> ...
>
> It must be a bug - isn't it ?
>
<snip/>

Looks like it. Originally, the spec didn't require (and therefore,
Commons SCXML didn't implement) <onentry> / <onexit> children of
<parallel>.

Please submit a smallest possible test case (and a patch, if you want)
to the Commons SCXML project in JIRA. Thanks!

-Rahul


> Regards
> Danny
>
>
> <?xml version="1.0"?>
> <scxml xmlns="http://www.w3.org/2005/07/scxml"; version="1.0"
>        xmlns:cs="http://commons.apache.org/scxml";
> initialstate="running">
>
>        <parallel id="running">
>                <onentry>
>                        <log expr="'We are in running'" />
>                </onentry>
>
>                <state id="state1">
>                        <onentry>
>                                <log expr="'We are in state1'" />
>                        </onentry>
>                </state>
>
>                <state id="state12" />
>        </parallel>
> </scxml>
>
> Caused by: java.lang.NullPointerException
>        at
> org.apache.commons.scxml.SCInstance.getContext(SCInstance.java:178)
>        at org.apache.commons.scxml.model.Log.execute(Log.java:102)
>        at
> org.apache.commons.scxml.semantics.SCXMLSemanticsImpl.executeActions(SCX
> MLSemanticsImpl.java:232)
>        at
> org.apache.commons.scxml.SCXMLExecutor.reset(SCXMLExecutor.java:252)
>        at
> org.apache.commons.scxml.SCXMLExecutor.go(SCXMLExecutor.java:351)
>        at
> de.dtnet.virtcenter.util.scxml.persistence.domain.StateMachine.go(StateM
> achine.java:231)
>        ... 23 more
> ... Removed 22 stack frames
>
>
> ---------------------------------------------------------------------
> 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]

Reply via email to