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: New Issue: <rethrow> of Fault Name and Fault Data Where Present


New Issue: <rethrow> of Fault Name and Fault Data Where Present

Description and Justification: The semantics of <rethrow> are quite 
specific about fault data but no explicit mention is made about the 
fault name of the original fault where present.  No references are found 
in Section 5, 10 or 12 where <rethrow> is addressed. Therefore, a minor 
editorial revision is suggested in Section 10.1 (i.e. in first sentence).

Proposal:
   * Change from:
         o 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 section 12.5.
           Fault Handlers).
   * Change to:
         o The <rethrow> activity is used in fault handlers to rethrow
           the fault they caught, i.e. the fault name and fault data of
           the original fault where present. 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
           section 12.5. Fault Handlers).






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