Return-Path: 
 <commons-user-return-19328-apmail-jakarta-commons-user-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-commons-user-archive@www.apache.org
Received: (qmail 24653 invoked from network); 29 May 2007 02:23:31 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 29 May 2007 02:23:31 -0000
Received: (qmail 90509 invoked by uid 500); 29 May 2007 02:23:31 -0000
Delivered-To: apmail-jakarta-commons-user-archive@jakarta.apache.org
Received: (qmail 90448 invoked by uid 500); 29 May 2007 02:23:31 -0000
Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:commons-user-unsubscribe@jakarta.apache.org>
List-Help: <mailto:commons-user-help@jakarta.apache.org>
List-Post: <mailto:commons-user@jakarta.apache.org>
List-Id: "Jakarta Commons Users List" <commons-user.jakarta.apache.org>
Reply-To: "Jakarta Commons Users List" <commons-user@jakarta.apache.org>
Delivered-To: mailing list commons-user@jakarta.apache.org
Received: (qmail 90436 invoked by uid 99); 29 May 2007 02:23:31 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 May 2007 19:23:31 -0700
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (herse.apache.org: domain of rahul.akolkar@gmail.com
 designates 64.233.166.183 as permitted sender)
Received: from [64.233.166.183] (HELO py-out-1112.google.com) (64.233.166.183)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 May 2007 19:23:26 -0700
Received: by py-out-1112.google.com with SMTP id u77so3163398pyb
        for <commons-user@jakarta.apache.org>;
 Mon, 28 May 2007 19:23:05 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed;
        d=gmail.com; s=beta;
        h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=dXufzQ/Ok3Luca3hBP12O5QFm97OnDdbCJTVVHDHQzzKu0kp4EPiYixzBW51v34ifo1LvN2cBZvzATOjB02DHBi84xg6yhaq15MJu+B97D+0If6zgb/7mbI80gKcGk+bmBQuQk1yE1CJHn8pV/RfjomPWRGvHdAjOMAX4xgMQYc=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=foO1CvMMkgzwkE0YGm+gJih5IlOwnmGH2kX7y8saUA59uo8AyzwRbeYyBfcFb9iTgDZsYqXshmkNjmxjYHwacrxxIn6qx0TGdQoXxHRbDUfZkChJk7/gkYDOMEZ5yOfPFn/rgLhMvzPo3jRv+cfLx6k1/c029vlFtmKaSmUGfKI=
Received: by 10.65.23.7 with SMTP id a7mr11731348qbj.1180405385153;
        Mon, 28 May 2007 19:23:05 -0700 (PDT)
Received: by 10.65.186.8 with HTTP; Mon, 28 May 2007 19:23:05 -0700 (PDT)
Message-ID: <ce1f2ea80705281923qb95fc22x52ff8045d0c9baae@mail.gmail.com>
Date: Mon, 28 May 2007 22:23:05 -0400
From: "Rahul Akolkar" <rahul.akolkar@gmail.com>
To: "Jakarta Commons Users List" <commons-user@jakarta.apache.org>
Subject: Re: [SCXML] Event types
In-Reply-To: <141013.77726.qm@web50909.mail.re2.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <141013.77726.qm@web50909.mail.re2.yahoo.com>
X-Virus-Checked: Checked by ClamAV on apache.org

On 5/28/07, Nestor Urquiza <nestoru@yahoo.com> wrote:
> <snip>
> Bits like <invoke>, are also "executable content", but the semantics
> are decoupled from the mechanics of state transitions.
> </snip>
> As far as I understand <invoke> is still an ongoing discussion from w3c draft right? I mean it is not clear still how invoke will accept parameters and how the result would be processed by the <onentry> or <onexit> contexts from where at the end of the row <invoke> will be used.
>
<snip/>

Correct, <invoke> has many details TBD. Results are processed in <finalize>.


> In any case even using invoke I do not see an alternative to <if> when talking about exceptions, meaning that seems like the approach I am finaly using is the only practical solution for WEB domain. Basically I call custom actions from <var> and I check for the returned value.
>
<snap/>

Yup, its a viable solution ATM.


> <snip>
> Discussions on priority are useful in event queues (prior to the point
> any event is being processed by the engine). In processing events, the
> state machine uses one or more events (immutable set) in every "step"
> (and any derived events get added to the front of the queue).
> </snip>
> I get it, priority should be used just to control which events will be executed before and which after but never as a mean of stopping the  precessing of  any other event. Also exeptions are not a way to go  IMO when using expression languages as SCXML does so far. Simply very basic structured programming is to be used there, and I say very basic since we have no serious thinking from w3c side to include ECMA scripting within <script> or as part of some code to be executed by <invoke> as a possible full featured programming language that will for example allow reuse (I am doing reuse using XML entities which has several disadvantages already posted in previous posts here and at www voice w3c forum).
>
<snip/>

Your feedback is appreciated here (as I'm sure it is on the other list).

-Rahul


> Thanks,
>
> -Nestor
>
>
>

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