Return-Path: 
 <commons-user-return-19281-apmail-jakarta-commons-user-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-commons-user-archive@www.apache.org
Received: (qmail 8423 invoked from network); 23 May 2007 02:41:05 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 23 May 2007 02:41:05 -0000
Received: (qmail 31218 invoked by uid 500); 23 May 2007 02:41:07 -0000
Delivered-To: apmail-jakarta-commons-user-archive@jakarta.apache.org
Received: (qmail 30823 invoked by uid 500); 23 May 2007 02:41:05 -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 30811 invoked by uid 99); 23 May 2007 02:41:05 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 May 2007 19:41:05 -0700
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received-SPF: pass (herse.apache.org: local policy)
Received: from [206.190.38.124] (HELO web50904.mail.re2.yahoo.com)
 (206.190.38.124)
    by apache.org (qpsmtpd/0.29) with SMTP; Tue, 22 May 2007 19:40:57 -0700
Received: (qmail 35505 invoked by uid 60001); 23 May 2007 02:40:36 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID;
  b=3bRptAxBB/LfO6bmndcRVtYVAzO9ZW0JIYY/8Nbx8C+u43IlW1Frod3AmZ54YLW/hShcSC7NcOu8mqw+O/ez1LxxDWFhFTSzdyqeVnLu02uvqGPPxGa6xZYAM+8MSjXJB9kfUDrM9U4Mz6JGycmADEXwohOpWX/ajikyGjR19C4=;
X-YMail-OSG: 
 _5ZiZzwVM1mp988aQ583N002c0xbhgFW5ufwmOeKPnpmWQaj1aM0NTEhd_7kP30rtgygUEt0xwCvk7ZZFb__b0B95EPk044PSYFiA6Xbr1nnKRKyuZjVjEZqO0tst6pxXYixLqmnv_tReYSieKTIjpzPqg--
Received: from [72.148.142.191] by web50904.mail.re2.yahoo.com via HTTP;
 Tue, 22 May 2007 19:40:36 PDT
X-Mailer: YahooMailRC/651.23.1 YahooMailWebService/0.7.41.14
Date: Tue, 22 May 2007 19:40:36 -0700 (PDT)
From: Nestor Urquiza <nestoru@yahoo.com>
Subject: Re: [SCXML] Event types
To: Jakarta Commons Users List <commons-user@jakarta.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ascii
Message-ID: <545551.34820.qm@web50904.mail.re2.yahoo.com>
X-Virus-Checked: Checked by ClamAV on apache.org

Could you mention in your opinion at least one of the alternatives to modify or create a new SCXML Semantic implementation to deal with critical errors that are supposed to stop the normal flow of the application? The Event type could be one that we already saw is not going to be provided within the library and still seems like the best way to accomplish that goal.

Thanks,

-Nestor

----- Original Message ----
From: Rahul Akolkar <rahul.akolkar@gmail.com>
To: Jakarta Commons Users List <commons-user@jakarta.apache.org>
Sent: Tuesday, May 22, 2007 3:47:17 PM
Subject: Re: [SCXML] Event types

On 5/22/07, Nestor Urquiza <nestoru@yahoo.com> wrote:
> So you mean commons-scxml users should provide their application specific SCXMLSemanticImpl.java? Which method should we use to use a custom one that lives in a different than org.apache.commons.scxml.semantics package?
>
<snip/>

No (well, depends on the specifics but that wouldn't be the first
course of action -- since that deviates from what is provided out of
the box).

To answer the other question, IIUC -- if custom SCXMLSemantics are
indeed defined, then the four argument SCXMLExecutor constructor needs
to be used.

I meant to say that event names (such as "app.error" in your example,
which should be called "error.app" IMO to better serve an event
ontology when using wild cards etc.), event types (trickier to get at)
and event payloads etc. often make more sense to the application
(rather than the library).

-Rahul


> Thanks,
>
> -Nestor
>
> ----- Original Message ----
> From: Rahul Akolkar <rahul.akolkar@gmail.com>
> To: Jakarta Commons Users List <commons-user@jakarta.apache.org>
> Sent: Monday, May 21, 2007 10:58:29 PM
> Subject: Re: [SCXML] Event types
>
> On 5/21/07, Nestor Urquiza <nestoru@yahoo.com> wrote:
> > Hi Rahul,
> >
> > Talking about this I do not know if I posted about it before ( lazy now to search in the archives ) but at some point I ( at least ) thought about a special event let us say "app.error" that I was hoping to use from a custom action for example to provide an "exception" mechanism.
> >
> > In a glance imagine your custom action needs to stop the normal course of your SCXML code. I was hoping to use the type ERROR to define a special event called "app.error" that would be included in the transition element to specify where to go when an unexpected exception occurs.
> >
> > My guess a while ago was that it would be great to make commons-SCXML "exception aware" meaning that if for some reason an event of ERROR type is raised the complete state machine would stop processing the current logic triggerred by a regular event and would then proceed to the transitions to move the FSM to a state corresponding to the error event transition target.
> >
> > Makes sense?
> >
> <snip/>
>
> Yes, users can leverage the event types (either existing or new /
> user-defined) to have application-specific semantics, as you indicate
> above. However, Commons SCXML itself does not use the type
> information.
>
> -Rahul
>
>
> > Thanks,
> >
> > -Nestor
> >
> > ----- Original Message ----
> > From: Rahul Akolkar <rahul.akolkar@gmail.com>
> > To: Jakarta Commons Users List <commons-user@jakarta.apache.org>
> > Sent: Monday, May 21, 2007 1:06:18 PM
> > Subject: Re: [SCXML] Event types
> >
> > On 5/20/07, Hanh-Missi Tran <Missi.Tran-han@lifl.fr> wrote:
> > > Hi
> > >
> > > A TriggerEvent object is associated with a type (CALL_EVENT,
> > > SIGNAL_EVENT, ..) but   I don't know what they are used for. I look in
> > > the source code but whenever an event is handled, its type is not used
> > > (I'm wrong ?). So can someone tell me what they may be used for ?
> > >
> > <snip/>
> >
> > You are correct, the type information is not used.
> >
> > One of the intents of providing that was to use it as potential basis
> > for priority (for example, a CHANGE_EVENT, since its usually a derived
> > event, would have a lower priority etc.) -- but that was never
> > realized in code (or spec).
> >
> > -Rahul
> >

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






      ____________________________________________________________________________________Fussy? Opinionated? Impossible to please? Perfect.  Join Yahoo!'s user panel and lay it on us. http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7 


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