[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [wsbpel] Issue - 287 - Proposal for Vote
AMENDMENT The previously submitted proposal is close to the original resolution of issue 162. However, the scope name uniqueness constraint specified there is still too restrictive and more difficult to enforce. As an alternative, I amend this proposal with the following new proposal which ***only*** enforces the uniqueness of the <compensateScope> activity. In section 10.1., ***delete*** "The name of a named activity MUST be unique amongst all named activities present within the same immediately enclosing scope. This requirement MUST be statically enforced." In section 12.4.3., ***add*** the following text as a new 4th paragraph: "The name of the activity referenced in the target attribute of the <compensateScope> activity MUST be unique. This requirement MUST be statically enforced." Kind Regards DK Dieter König Mail: dieterkoenig@de.ibm.com IBM Deutschland Entwicklung GmbH Senior Technical Staff Member Tel (office): (+49) 7031-16-3426 Schönaicher Strasse 220 Architect, Business Process Choreographer Fax (office): (+49) 7031-16-4890 71032 Böblingen Member, Technical Expert Council Tel (home office): (+49) 7032-201464 Germany
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]