Two additional changes to the 221 resolution (friendly amendments):

(A) First sentence: Drop "during termination of a scope, " (B) Appendix A (missingReply standard fault):

Result:

(A) Add to the end of 14.4:

-------- The standard fault bpws:missingReply can also be detected if one or more receive operations using a partner link or message exchange defined in the scope remain open. (1) If the contained activity and the event handlers of the scope have completed then a check for missing replies MUST be made. If one is detected then a bpws:missingReply is thrown. The scope itself can catch it as this is still inside of the scope. (2) If a fault handler (for a different fault) has completed then a check for missing replies MUST be made. If one is detected then a bpws:missingReply is thrown to the parent scope (similar to throwing or rethrowing other faults from a fault handler). (3) If a fault handler itself throws or rethrows a different fault to the parent scope then no check for missing replies is made, so a bpws:missingReply is potentially lost (similar to a case where multiple faults have been detected and only one gets propagated). (4) If the termination handler is executed then no check for missing replies is made, so a bpws:missingReply is potentially lost (like any other fault thrown in the termination handler).

--------

(B) Change Appendix A (missingReply standard fault) from:

-------- Thrown when a receive has been executed, and the process instance reaches the end of its execution without a corresponding reply having been executed.

-------- To:

-------- Thrown when a receive has been executed, and the process instance or a scope reaches the end of its execution without a corresponding reply having been executed.

--------

Kind Regards DK

----- Forwarded by Dieter Koenig1/Germany/IBM on 25.01.2006 17:39 -----

Dieter Koenig1/Germany/I BM To wsb...@lists.oasis-open.org 19.01.2006 17:58 cc

Subject [wsbpel] Issue - 221 - Proposal vor Vote

The last paragraph of section 14.4. "Web Service Operations" (starting with "The fourth extension ...") introduces the standard fault "bpws:missingReply".

Add the following text to the end of the paragraph:

-------- The standard fault bpws:missingReply can also be detected during termination of a scope, if one or more receive operations using a partner link or message exchange defined in the scope remain open. (1) If the contained activity and the event handlers of the scope have completed then a check for missing replies MUST be made. If one is detected then a bpws:missingReply is thrown. The scope itself can catch it as this is still inside of the scope. (2) If a fault handler (for a different fault) has completed then a check for missing replies MUST be made. If one is detected then a bpws:missingReply is thrown to the parent scope (similar to throwing or rethrowing other faults from a fault handler). (3) If a fault handler itself throws or rethrows a different fault to the parent scope then no check for missing replies is made, so a bpws:missingReply is potentially lost (similar to a case where multiple faults have been detected and only one gets propagated). (4) If the termination handler is executed then no check for missing replies is made, so a bpws:missingReply is potentially lost (like any other fault thrown in the termination handler).

Kind Regards DK