[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