[wsbpel] Issue - R8 - Revised Proposal

The compensation handler for an isolated scope does not share the isolation domain of the associated scope. The isolation domain ends and the scope snapshot is created when the normal processing of that isolated scope completes. Afterwards, the compensation handler is installed. If the invoker of the compensation handler (i.e. <compensate> / <compensateScope> activities or implicit invoking FCT-handler of the immediately enclosing scope) is not within an isolation domain, the execution of the compensation handler associated with an isolated scope will be implicitly isolated. Such an implicit isolation domain ends when the execution of such a compensation handler ends. (See scope "FH_P" and scope "Q" in the example below.) If the invoker of the compensation handler is already within an isolation domain and the invoked compensation handler is associated with an isolated scope, such a scope definition is a case of nested isolated scopes and MUST be disallowed by static analysis. (If scope "FH_P" below is isolated, then such a scope definition is disallowed.) (See also [SA00091])