W3C home > Mailing lists > Public > www-voice@w3.org > October to December 2011

Re: SCXML entry order

From: Carlos Verdes <cverdes@gmail.com>
Date: Tue, 6 Dec 2011 11:16:19 +0000
Message-ID: <CAMZOHDMQW4Ct7yraWF0=fRfrgnvrbTROavPYd1JfH-zNFtNYaQ@mail.gmail.com>
To: DOLECEK Ales <Ales.Dolecek@nextiraone.eu>
Cc: "www-voice@w3.org" <www-voice@w3.org>
I see, I confuse send and raise with send and invoke.
I reread and realize the difference, one simply sends an event and the
other instance a service.

Thanks.

On 6 December 2011 09:07, DOLECEK Ales <Ales.Dolecek@nextiraone.eu> wrote:

> **
> Invoke is NOT executable content. This means that <invoke> is not legal
> under <onentry> nor any other element that holds executable content.
>
> Ales
>
>  ------------------------------
> *From:* Carlos Verdes [mailto:cverdes@gmail.com]
> *Sent:* Tuesday, December 06, 2011 12:12 AM
> *To:* Jim Barnett
> *Cc:* www-voice@w3.org
> *Subject:* Re: SCXML entry order
>
> Hi,
>
> First of all thanks for your answer.
>
> I have another question... if a State has on entry and on exit elements...
> and this elements  have executable content so could make an invoke... why
> do the state has the invoke element apart?
>
> From my point of view this invoke is redundant and it doesn't specify when
> you should call it (you have to check the algorithm), to it shouldn't be a
> children of a state (just a children of on entry or on exit element).
>
> Regards,
> Carlos Verdes.
>
>
Received on Tuesday, 6 December 2011 11:16:55 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 6 December 2011 11:17:01 GMT