[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [wsbpel] Issue 303 resolution
Issue 303 was approved in the July 26 call. The resolution included the following changes: #1 Change paragraph in Section 12.5 (line 5118 of version 1.163) From: Because of the flexibility allowed in expressing the faults that a <catch> construct can handle, it is possible for a fault to match more than one fault handler. To: Because of the flexibility allowed in expressing the faults that a <catch> construct can handle, it is possible for a fault to match more than one fault handler. While multiple fault handlers may match a fault, the <faultHandlers> element MUST NOT contain identical <catch> constructs. The <catch> constructs are considered identical in this context, when they have identical values in their faultName, faultElement and faultMessageType attributes. If an attribute is not present in a <catch>, its value is considered absent and is identical only to an absent attribute of another <catch>. A process definition that violates this condition MUST be detected by static analysis and MUST be rejected by a conformant implementation. #2 Add an entry to the static analysis table [SA000??] Identical <catch> constructs MUST NOT exist within a <faultHandlers> element.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]