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. The compensation handler actually shares the isolation domain of the invoking activities (i.e. <compensate> / <compensateScope>) or implicit invoking FCT-handler of the immediately enclosing scope, when the invoker of the compensation handler is already within an isolation domain. (See scope "FH_A" in the following examples.) If the invoker of the compensation handler is not within an isolation domain, the execution of the compensation handler for an isolated associated 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".) 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 one of cases of nested isolation and MUST be disallowed by static analysis. (See also [SA00091])
