Return-Path: 
 <user-return-19861-apmail-commons-user-archive=commons.apache.org@commons.apache.org>
Delivered-To: apmail-commons-user-archive@www.apache.org
Received: (qmail 40086 invoked from network); 5 Sep 2007 18:07:33 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 5 Sep 2007 18:07:33 -0000
Received: (qmail 68617 invoked by uid 500); 5 Sep 2007 18:07:23 -0000
Delivered-To: apmail-commons-user-archive@commons.apache.org
Received: (qmail 68282 invoked by uid 500); 5 Sep 2007 18:07:22 -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 68273 invoked by uid 99); 5 Sep 2007 18:07:22 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Sep 2007 11:07:22 -0700
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 209.85.132.247 as permitted sender)
Received: from [209.85.132.247] (HELO an-out-0708.google.com) (209.85.132.247)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Sep 2007 18:07:17 +0000
Received: by an-out-0708.google.com with SMTP id d17so471562and
        for <user@commons.apache.org>; Wed, 05 Sep 2007 11:06:57 -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=H2ZYQy3pLBfn5q/Xmz6YYN47/yq+xN+8+DFREDbBFHZsiBVnOhP47YvnmzYoLdoDcAgqHOnNrRFPwozEFHsbR4hiqQBIiPfeWu0DQko2aAIx92lKWfI1AYKaa+1AhLSHCYrruH9VegeXZJk3ePhgE+hle1qs0AiD3d+l+CWAPEU=
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=FqQjm9MD+RQFSW191i6/5OTl0tepwbBBPUkr5S/rYgFBa638jvb3sQLLv1/w5gL6MQiYRuY29XlzLSWGPFBX291/7HYMw4yhH7Ljgb5vlxwstf5H5u2vzlitCZCRald9NqlYVTh4FbQU8EyobTk9I8BVlbrqu+0A+tDd6L5sJdk=
Received: by 10.100.95.19 with SMTP id s19mr6182661anb.1189015616716;
        Wed, 05 Sep 2007 11:06:56 -0700 (PDT)
Received: by 10.100.191.4 with HTTP; Wed, 5 Sep 2007 11:06:56 -0700 (PDT)
Message-ID: <ce1f2ea80709051106k11fd76f1p2d99c988617936d2@mail.gmail.com>
Date: Wed, 5 Sep 2007 14:06:56 -0400
From: "Rahul Akolkar" <rahul.akolkar@gmail.com>
To: "Jakarta Commons Users List" <user@commons.apache.org>
Subject: Re: [SCXML] questions on event ids and finalize
In-Reply-To: 
 <517A8C7A47847940B09AA7B7044C740B01088E78@scexch01.sc.ad.terayon.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: 
 <517A8C7A47847940B09AA7B7044C740B01088E78@scexch01.sc.ad.terayon.com>
X-Virus-Checked: Checked by ClamAV on apache.org

On 9/4/07, Cook, Dennis <dennis.cook@terayon.com> wrote:
> I have a few questions
>
>
>
> 1.      The spec indicates that an invoked service must return a
> ''id.Done' event , (where the 'id' is the id for this invocation).  But
> I noticed the SimpleSCXMLInvoker is returing a "id.invoke.done" event
> when done and a "id.invoke.cancel.response" event in response to the
> cancel.  The spec indicates that format as TBD.  So what is the proper
> format for the done event.  Is it "id.Done" as spec'ed or
> "id.invoked.done" as the SimpleSCXMLInvoker uses?
<snip/>

We won't know until the spec has the TBD there. But IMO, it clearly
shouldn't be "id.done" since that already has a (different) meaning --
in particular, it indicates that a final substate has been reached for
a composite state. Therefore, "id.invoke.done" was used in the Commons
implementation (and it is subject to change based on spec changes).


> 2.      I cannot figure out how to get a <finalize> block to execute any
> content.  I have tried a <log> entry, but it never seems to be executed.
> I  found a test case org.apache.commons.scxml.invoke.InvokeTest.java
> which also includes a <final> element.  This is not getting executed
> either.  Is this a known bug?
>
<snap/>

Thanks for taking time to look at the test cases, it makes the
discussion easier. The particular test case you mention
[testInvoke01Sample() in the file above] is a bit incomplete in terms
of <finalize> (it is complete in terms of what its testing -- which is
ensuring the context of the invoked state machine is populated
correctly). In order to execute the <finalize> block, the invoked
state machine needs to run to completion. That can be done by adding
the following line as the last statement of the try block:

 SCXMLTestHelper.fireEvent(exec, "invoked.next");

This will drive the invoked state machine (invoked-01.xml) to
completion, cause the <finalize> to execute, the corresponding
"id.invoke.done" event to be triggered and the gating transition to be
followed to the "end" state.

-Rahul


>
>
> Dennis Cook
>
> Motorola - Home & Network Mobility
>
> Sr. Staff Software Engineer
>
> (o) (408) 235-5874
>
> (c) (408) 515-4799
>
>

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