Return-Path: 
 <user-return-20408-apmail-commons-user-archive=commons.apache.org@commons.apache.org>
Delivered-To: apmail-commons-user-archive@www.apache.org
Received: (qmail 72768 invoked from network); 30 Dec 2007 05:56:03 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 30 Dec 2007 05:56:03 -0000
Received: (qmail 25840 invoked by uid 500); 30 Dec 2007 05:55:45 -0000
Delivered-To: apmail-commons-user-archive@commons.apache.org
Received: (qmail 25756 invoked by uid 500); 30 Dec 2007 05:55:45 -0000
Mailing-List: contact user-help@commons.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@commons.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@commons.apache.org>
List-Post: <mailto:user@commons.apache.org>
List-Id: <user.commons.apache.org>
Reply-To: "Jakarta Commons Users List" <user@commons.apache.org>
Delivered-To: mailing list user@commons.apache.org
Received: (qmail 25747 invoked by uid 99); 30 Dec 2007 05:55:44 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 29 Dec 2007 21:55:44 -0800
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of rahul.akolkar@gmail.com
 designates 72.14.220.157 as permitted sender)
Received: from [72.14.220.157] (HELO fg-out-1718.google.com) (72.14.220.157)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 30 Dec 2007 05:55:23 +0000
Received: by fg-out-1718.google.com with SMTP id 22so2606715fge.24
        for <user@commons.apache.org>; Sat, 29 Dec 2007 21:55:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        bh=0QwBdcWD82zB0hLrqBraJ52nuutKYHfnimjNx14O3Xg=;
        b=RHxE95+Ri26R6/aHiGBFjzTq3cNdBYqfGI2xTu564EOh81VM6lryKNeZgMtVBNMHhFJr9MYIT9cFh5mF4P4jFoVh7kKod8UEsoRdWU+Hl99zgHs8THT9HSxhPLniN7eLCHEl0kKhPxnAWLKtw9lJkSe+XjR+WgWUi2f0pY8w6qk=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=kTRN1yDT77rxP9XhA+9V5kKcsinIe+4okoENUQHboMyjLjMNykoD/FbzUMNXieGF7HBjziZuaEEGf9s7l4yVSi+hnEz+GvT/OE9K3c1y2WB2wjf+UbY9zY7a9Uobx7kS9VuFaX82Yv6nt0UHCR+yqDvprpDoe/icZ4XmqLkMNTs=
Received: by 10.82.184.2 with SMTP id h2mr19787524buf.22.1198994126729;
        Sat, 29 Dec 2007 21:55:26 -0800 (PST)
Received: by 10.82.140.3 with HTTP; Sat, 29 Dec 2007 21:55:26 -0800 (PST)
Message-ID: <ce1f2ea80712292155m6740f3bbj159141dc32145846@mail.gmail.com>
Date: Sun, 30 Dec 2007 00:55:26 -0500
From: "Rahul Akolkar" <rahul.akolkar@gmail.com>
To: "Jakarta Commons Users List" <user@commons.apache.org>
Subject: Re: SCXML
In-Reply-To: <2f0968250712291224v713c32b1n3e65b244fb2c0f1e@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <2f0968250712281426v78a192a8s85babe55a8f7d658@mail.gmail.com>
	 <ce1f2ea80712281505g71c8f97epf9b261dff1265b16@mail.gmail.com>
	 <2f0968250712291224v713c32b1n3e65b244fb2c0f1e@mail.gmail.com>
X-Virus-Checked: Checked by ClamAV on apache.org

On 12/29/07, Lupu Slobodu <lupu.slobodu@gmail.com> wrote:
> Thanks, it looks that the '_eventdata' is  available as a root context
> variable(not in the state's S2 local context thought)
>
<snip/>

Yup, and it wouldn't make much sense in S2's local context -- for
example, it would also have to be in the local context of any state S
such that S belongs to LCA(S1,S2).

All contexts should ultimately delegate to the root.

-Rahul


> On Dec 28, 2007 6:05 PM, Rahul Akolkar <rahul.akolkar@gmail.com> wrote:
>
> > Please use descriptive email subjects. The convention (since this is a
> > shared mailing list) is to use [SCXML] as a prefix followed by a
> > suitable subject. It also helps the archives to have better subjects.
> >
> > On 12/28/07, Lupu Slobodu <lupu.slobodu@gmail.com> wrote:
> > > Suppose the event E1 triggered a state machine transition from S1 to S2.
> > How
> > > can one make this event (more precisely it's payload) available for the
> > > actions being executed by the state  S2?
> > >
> >
> > If the actions are within S2's <onentry>, you can access the payload
> > as the special variable '_eventdata'.
>
>
> > If the actions are in other executable content, you'll need to persist
> > the payload in a <datamodel> (either S2 or ancestors) using suitable
> > <assign> statements when the payload is accessible (such as, in S2's
> > <onentry>).
> >
> > -Rahul
> >

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
For additional commands, e-mail: user-help@commons.apache.org