OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsbpel message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Issue - 260 - [Fwd: Re: Chapter 11 review meeting scheduled (wordingfor Issue 260)]



Hi all,

Resend with a proper subject line ... Just in case if we need to discuss in the F2F next week.

Thanks!


Regards,
Alex Yiu


-------- Original Message --------
Subject: Re: Chapter 11 review meeting scheduled (wording for Issue 260)
Date: Tue, 25 Apr 2006 02:08:42 -0700
From: Alex Yiu <alex.yiu@oracle.com>
To: Alex Yiu <alex.yiu@oracle.com>
CC: Marin, Mike <MMarin@filenet.com>, Danny van der Rijn <dannyv@tibco.com>, Dieter Koenig1 <dieterkoenig@de.ibm.com>, Diane Jordan <drj@us.ibm.com>, Simon D Moser <SMOSER@de.ibm.com>, Alex Yiu <alex.yiu@oracle.com>
References: <69FB2CA668C6D841BE0326C13071C69F0619F8B8@hq-ex2kpo1.filenet.fn.com> <444D0593.8010004@oracle.com>



Hi, all,

Last time we stopped around: "Suppressing the bpel:joinFailure fault is similar to surrounding each affected activity with a  activity that defines an empty faultHandler for the bpel:joinFailure fault. For example, the following:"

... right before rewording a couple of paragraphs needed for Issue 260 ...

Here are my suggested changes (highlighted in GREEN) for discussion tomorrow:

From:
------------------------------
<process...>
   <scope name="invokeA">
       <faultHandlers>
           <catch faultName="bpel:joinFailure">
                <empty/>
            </catch>
       </faultHandlers>
       <invoke name="invokeA" ... />
          <targets> <target ... /> </targets>
       </invoke>
   </scope>
</process>

------------------------------

To:
------------------------------
<process...>
   <scope name="virtual scope">
       <faultHandlers>
           <catch faultName="bpel:joinFailure">
                <empty/>
            </catch>
       </faultHandlers>
       <invoke name="invokeA" ... />
          <targets> <target ... /> </targets>
       </invoke>
   </scope>
</process>

------------------------------

From:
------------------------------
The faultHandler behavior is an <empty> activity, that is, the faultHandler suppresses the
fault and does nothing about it. Note that
------------------------------

To:
------------------------------
The faultHandler behavior is an <empty> activity, that is, the faultHandler suppresses the
fault and does nothing about it. Note that the "virtual scope" mentioned above only is just for illustration only and is not meant for normative semantics equivalence. Except suppressing join failure, this "virtual scope" does not carry any other scope-related semantics, such as compensation.
------------------------------

From:
------------------------------
The name of the scope created to suppress the bpel:joinFailure fault that immediately
encloses an activity with a join condition is the same as the name of the activity itself. In
case of an <invoke> activity (see 10.3. Invoking Web Service Operations) with an inlined
fault or compensationHandler, join failure suppression is applied to the implied scope of
the <invoke> activity. Effectively two scopes are implied: an outer scope containing an
empty faultHandler for the bpel:joinFailure fault and an inner scope containing the
links, faultHandlers, and compensationHandlers of the original <invoke> activity.
Identical rules apply to <scope> activities: a <scope> with join failure suppression
enabled implies an additional surrounding scope.
------------------------------

To:
------------------------------
The name of the scope created to suppress the bpel:joinFailure fault that immediately
encloses an activity with a join condition is the same as the name of the activity itself.
In
case of an <invoke> activity (see 10.3. Invoking Web Service Operations) with an inlined
fault or compensationHandler, join failure suppression is applied to the implied scope of
the <invoke> activity. Effectively two scopes are implied: an outer "virtual scope"
containing an empty faultHandler for the bpel:joinFailure fault and an inner scope containing the links, faultHandlers, and compensationHandlers of the original <invoke> activity.
To highlight the contrary again, the inner implied scope is indeed a real scope with all scope related semantics without the actual <scope> syntax, while the outer "virtual scope" does not carry any real scope semantics (e.g. compensation) except suppressing join failure.
Identical rules apply to <scope> activities: a <scope> with join failure suppression
enabled implies an additional surrounding
"virtual scope". That is, when join failure happens, the inner scope does not even get started.

------------------------------


Thanks!



Regards,
Alex Yiu


Alex Yiu wrote:

Hi all,

You guys may have received a sperate email about the web conference info for tomorrow meeting (8am PDT) already.

Here let I repeat the email:

Web Conf Info:
-----------------------------
https://conference.oracle.com/imtapp/app/sch_mtg_details.uix?mID=43083899
Web Conference ID: 43083899
Web Conference Key: bpel
-----------------------------

Conf Phone Info:
-----------------------------
Meeting ID: 385302
Meeting Password 7654321

MeetingPlace Access Numbers From the AMER region dial:
. 1-888-967-2253
. +1-650-607-2253
From the APAC region dial:
. +61 2 8817 6100
From the EMEA region dial:
. +44 118 924 9000
-----------------------------


Thanks!


Regards,
Alex Yiu






[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]