OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

wsbpel message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: changes to rethrow wording

Peter, please open an issue for this, and move it to closed and applied immediately based on proposal and vote at the F2F.  

Text in 10.11 was corrected to add normative "MUST" wording:    

The <rethrow> activity is used in fault handlers to rethrow the fault they caught. It can be used only within a fault handler (<catch> and <catchAll>). Modifications to the fault data MUST be ignored by <rethrow>. For example, if the logic in a fault handler modifies the fault data and then call <rethrow>, the original fault data would be rethrown and not the modified fault data. Similarly if a fault is caught using the shortcut that allows message type faults with one part defined using an element to be caught by fault handlers looking for the same element type, then a <rethrow> would rethrow the original message type data  (See 12.4. FaultHandlers).

Also text was moved to section 5.2 from 12.4, "This syntatic constraint must  be statically enforced."    Resulting in:  

The <rethrow> activity is used to rethrow the fault that was originally caught by the immediately enclosing faultHandler. The <rethrow> activity MUST only be used within a faultHandler (i.e. <catch> and <catchAll> elements). This syntatic constraint must  be statically enforced.  

Regards, Diane
IBM  Emerging Internet Software Standards
(919)254-7221 or 8-444-7221, Mobile: 919-624-5123, Fax 845-491-5709

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]