Reg. Issue#3 Proposal

["Muruga Chinnananchi" <muruga@collaxa.com>]

Hi all,

I have one question regarding Issue #3 which has been resolved. The Proposal
text says the following:
(http://www.oasis-open.org/committees/download.php/5197/wsbpel_issues_list.h
tml#Issue3):

"The behavior of a compensation handler can be thought of as an optional
continuation of the behavior of the associated scope and as such its usage
of variables is similar to the usage that occurred in the body of the scope
itself, including update actions. This includes variables in both the local
scope and all enclosing scopes. Note that the compensation handler may
itself have been called from an enclosing compensation handler. It will then
share the continuation of the state of the enclosing scope that its caller
is using. In the attached picture showing three nested scopes S1, S2 and S3,
and their compensation handlers C1, C2, C3, and failure handlers F1 and F2,
we may have an error handling call stack F1->C2->C3. In that case C3 will
share the state of S2 as it is being seen and used by C2."


But When I looked the latest spec dated 23 Nov 2003, I noticed that this
proposal has been updated in the spec. But the text differs little bit from
the original proposal. I highlighted the addition under the <NEW> tag.

"The behavior of a compensation handler can be thought of as an optional
continuation of the behavior of the associated scope and as such its usage
of variables is similar to the usage that occurred in the body of the scope
itself, including update actions.   This includes variables in both the
local scope and all enclosing scopes. <NEW>For the variables in the local
scope, the compensation handler starts with the scope snapshot.</NEW> Note
that the compensation handler may itself have been called from an enclosing
compensation handler.  It will then share the continuation of the state of
the enclosing scope that its caller is using.  In the picture below showing
three nested scopes S1, S2 and S3, and their compensation handlers C1, C2,
C3, and failure handlers F1 and  F2, we may have an error handling call
stack F1->C2->C3.  In that case C3 will share the state of S2 as it is being
seen and used by C2, and the current state of the uncompleted scope S1."

Can I assume that when compensation handler runs for a Scope, it can only
see the snapshot of the scope? I think this snapshot is missing in the
original proposal.