new issue: language in 12.3.3.1 addressing name uniqueness for target scope/activities of <compensateScope>

Section 12.3.3.1, Compensation of a Specific Scope,
states in paragraph 3 that "All scopes and activities directly nested in a
scope (i.e. not within a nested scope) MUST be uniquely named. If the value of the
target attribute specified on a compensateScope activity does not resolve to a
unique scope or activity name in the same scope as the compensateScope
activity, the WS-BPEL definition MUST be rejected from processing. This
requirement MUST be statically enforced."  

 

However, this does not reflect the resolution to
Issue 162 [1] as amended by [2] in a manner consistent with Section 10.1. We
need to properly reflect that the restrictions on name uniqueness for scopes
and invoke activities apply specifically to those referenced by a
<compensateScope> activity. 

 

To resolve this, we need to delete the paragraph 3 of
Section 12.3.3.1 and replace it with the following:

 

"The names of all named activities immediately
enclosed in a scope must be unique (see section 10.1. Standard Attributes for
Each Activity). The target attribute of a <compensateScope> activity MUST
refer to a scope or an invoke activity with a fault handler or compensation
handler. The referenced activity MUST be immediately enclosed by the scope
containing the FCT-handler with the <compensateScope> activity. If these
requirements are not met then the WS-BPEL process MUST be rejected. These
requirements MUST be statically enforced."

 

[1] http://lists.oasis-open.org/archives/wsbpel/200412/msg00061.html

[2] http://www.oasis-open.org/apps/org/workgroup/wsbpel/download.php/10988/BPEL%20minutes%20Dec%2014%20to%2016%20f2f.htm#_Toc93207991

 

--

 

  
  
   

    
    

    
    
    

    
Charlton Barreto

    Sr .Computer Scientist

    Adobe Systems Incorporated

    345 Park Avenue, MS E15

San Jose, CA
     95110-2704 USA

    408.536.4496 p   

    415.692.5396 v

     

    

    
   

  
  

  
 

 

smime.p7s