Hi Ivana,
#1: What I mean is the count of branches is calculated only once and won't
change as the result of the flow execution. For example:
<completionCondition>
<branches>$myN</branches>
</completionCondition>
The expression $myN is calculated at the start of the flow/pfe. And the
count of completed activities is tested against this count after each
activity completion within the flow/pfe.
#3: I think the text I am referring to is the stuff about "termination
handlers not being able to rethrow since the parent of the scope is already
faulting..." that is no longer the case since this termination is being done
not because of a fault but a completion. So for example if a child of the
flow is a scope that didn't complete and the completion condition is reached
then it will be terminated. Therefore it's termination handler will execute
if the termination handler faults what should happen. The current text in
13.4.4 is at least misleading.
#4: Let me think some more about it.
Thanks,
Chris
-----Original Message-----
From: Trickovic, Ivana [mailto:]
Sent: Wednesday, September 14, 2005 1:56 PM
To: Chris Keller ;
Cc:
Subject: RE: [wsbpel] Issue 6.2 - Updated Proposal For Vote
Hi Chris,
#1: How about to add in (5) the following:
"... a completionCondition
element the completion condition is evaluated each time AFTER a directly
enclosed activity completes."
