Return-Path: 
 <commons-user-return-15724-apmail-jakarta-commons-user-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-commons-user-archive@www.apache.org
Received: (qmail 41998 invoked from network); 4 Apr 2006 19:27:59 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 4 Apr 2006 19:27:59 -0000
Received: (qmail 22518 invoked by uid 500); 4 Apr 2006 19:27:53 -0000
Delivered-To: apmail-jakarta-commons-user-archive@jakarta.apache.org
Received: (qmail 22458 invoked by uid 500); 4 Apr 2006 19:27:53 -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 22447 invoked by uid 99); 4 Apr 2006 19:27:53 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Apr 2006 12:27:53 -0700
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: domain of rahul.akolkar@gmail.com
 designates 64.233.162.203 as permitted sender)
Received: from [64.233.162.203] (HELO zproxy.gmail.com) (64.233.162.203)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Apr 2006 12:27:51 -0700
Received: by zproxy.gmail.com with SMTP id 18so2018823nzp
        for <commons-user@jakarta.apache.org>;
 Tue, 04 Apr 2006 12:27:31 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=mZuRSlT78wD0KdBXjpU0VH0ntxJwwuqiDiAeWileswUxCSqGOfraVzK75MAsoeJb7LlYBmSxZczcVa/lwR/jXYpMZMGF9u3czdDUvDQXktvNoiIRXh3MTElmJ4ogRObLKJNBePNkkHRemQSAOoJoTaHvt87TpMvzdGfikqDlrnw=
Received: by 10.35.18.4 with SMTP id v4mr501344pyi;
        Tue, 04 Apr 2006 12:27:31 -0700 (PDT)
Received: by 10.35.40.1 with HTTP; Tue, 4 Apr 2006 12:27:31 -0700 (PDT)
Message-ID: <ce1f2ea80604041227m577bd1cbs33e5b760862b7f82@mail.gmail.com>
Date: Tue, 4 Apr 2006 15:27:31 -0400
From: "Rahul Akolkar" <rahul.akolkar@gmail.com>
To: "Jakarta Commons Users List" <commons-user@jakarta.apache.org>
Subject: Re: mailing list search capability available?
In-Reply-To: <20060404161653.72391.qmail@web50903.mail.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <20060404161653.72391.qmail@web50903.mail.yahoo.com>
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

On 4/4/06, Nestor Urquiza <nestoru@yahoo.com> wrote:
> Hi everyone,
> someone please could give me a hint on how to look for
> a keyword with the mailing list?
> I am trying to look in all threads at
> http://mail-archives.apache.org/mod_mbox/jakarta-commons-user/
> for some posts about anyone having experience on using
> commons scxml in business protocol implementations.
<snip/>

In addition to Kai's suggestion, you can also try MARC [1] or nabble
[2], which have better searching capabilities.

Using Commons SCXML for managing state-based behavior in any domain is
clean, and backed by an emerging W3C standard, so is a value-add. In
addition, I'm aware that UML profiles exist for automated business
processes -- there have also been UML to BPEL4WS mappings, for
example.


> In
> a glance I am planning to use SCXML for building
> strict business rules clients must meet in order to
> interact with a backend api. States are clearly needed
> because clients have persmissions to make http
> specific calls only after they meet criterias and come
> from other valid states.
<snap/>

If you end up applying Commons SCXML in a new domain, while it may
require some thought upfront, it gets you a lasting, extensible
solution. If you have specific questions on Commons SCXML, please
prefix the email subject with [SCXML]. The Commons SCXML website [3]
also has some usage notes and usecases.

-Rahul

[1] http://marc.theaimsgroup.com/?l=3Djakarta-commons-user
[2] http://www.nabble.com/Commons---User-f319.html
[3] http://jakarta.apache.org/commons/sandbox/scxml/


> Thanks a lot
> Nestor
>

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