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: Re: [wsbpel] Issue - R26 - Default Compensation Order Conflict



Hi, all,

Clarification wordings to be considered to be added to section 12.5.2
--------------------------------
Consider this situation: A scope "S0" which has child scopes "S1" and 
"S2", which in turn have child scopes "S1A" and "S2A" respectively. 
Also, there are control link dependency from "S1A" to "S2A" (i.e. a 
control link with "S1A" as source and "S2A" as target).  All these 
scopes have default FCT Handlers.

Scope "S0" receives a fault signal and terminates "S1" which is still 
running with "S1A" already completed and then compensate "S2" which is 
already completed.

It is noteworthy that the default compensation order used in the 
termination handler of "S1" and the default compensation order used in 
the compensation handler of "S2" are considered two disjoint default 
compensation orders. In spite of the control dependency, the 
compensation of "S1A" may happen before that of "S2A", because Rule 1 
above does not apply here as they happen in two disjoint compensation 
orders.

Similar situation happens when "S1" receives a fault signal, if "S2" and 
"S1A" are already completed. The compensation of "S1A" may happen before 
that of "S2A", as the default compensation order used in the fault 
handler of "S1" and the default compensation order used in fault handler 
of "S0" (which in turn causes the compensation of "S2A") are considered 
two different default compensation orders.
--------------------------------

Thanks!


Regards,
Alex Yiu



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