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 229 - Proposal for vote


Title: Issue 229 - Proposal for vote

This is the updated proposal incorporating Dieters suggested text and the clarification that no implicit child compensation will be performed.  Note that Issues 217 should be linked to 229 for discussions related to renaming the <compensate/> (i.e. compensate with no explicit scope).

Issue 229

Proposal Summary: Allow <compensate/> after <compensate scope="Sx"/> and emphasize that user defined fault and compensation handlers must explicitly call compensate for child scope compensation to occur.

Changes to current specification

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

Section 13.3.3

"...Note that the <compensate/> activity in a fault or compensation handler attached to scope S causes the default-order invocation of compensation handlers for completed scopes directly nested within S. The use of this activity can be mixed with any other user-specified behavior except the explicit invocation of <compensate scope="Sx"/> for scope Sx nested directly within S. Explicit invocation of compensation for such a scope nested within S disables the availability of default-order compensation, as expected."

Change to:


"User-defined fault handlers, compensation handlers, or termination handlers may use <compensate scope="..."> to compensate a specific child scope and/or <compensate/> to compensate all child scopes in default order. Any repeated attempt to compensate child scopes is treated as a no-op. If user-defined fault handlers, compensation handlers, or termination handlers do not use the compensate activity no child scope compensation will be performed."


Section 14.6

--- Remove this section as it is not applicable per issue 209 resolution ---

 

Appendix A -

--- Remove repeatedCompensation fault as it is not applicable per issue 209 resolution ---



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