R26 Default Compensation Order Conflict

1
R26 Default Compensation Order Conflict
FH
S0
1
2
4
TH
CH
S1
S2
E
3
5
CH
CH
A
B
2
R26 Default Compensation Order Conflict
FH
S0
4
3
CH
FH
S1
S2
2
5
1
CH
CH
F
A
B
3
R26 Default Compensation Order Conflict

• Don't change the behavior
• Accept default compensation order conflicts
• Explain conflict scenarios (Alex provides text ?)
  
• Change runtime behavior
• Promote control dependency to enclosing scope
• Disallow processes with conflicts
• Excludes many permeable scope scenarios
• Change termination model
• Defer compensation

4
R26 Default Compensation Order Conflict
S0
S1
S2
A
B
5
R26 Default Compensation Order Conflict

• The default compensation order is initiated by
  default termination handlers and default fault
  handlers, and recursively carried forward by
  compensation handlers. The termination phase
  always precedes the fault handling phase (see
  section 12.6. Termination Handlers). This
  sequence must not create a conflict with the
  default compensation order of scopes that are in
  a control dependency relationship. If scope "S2"
  has a direct peer-scope dependency on scope "S1",
  caused ba a scope "A" contained in "S1" and a
  scope "B" contained in "S2" where "B" has a
  control dependency on "A" then a WS-BPEL
  processor MUST execute these scopes as if "B" had
  a control dependency on scope "S1".