W3C home > Mailing lists > Public > www-ws-desc@w3.org > July 2004

Issue 233: Dynamically Override Fault Destinations (proposal)

From: Mark Nottingham <mark.nottingham@bea.com>
Date: Mon, 5 Jul 2004 13:47:29 -0700
Message-Id: <881023D0-CEC4-11D8-8B38-000A95BD86C0@bea.com>
To: Web Services Description <www-ws-desc@w3.org>

Issue 223 [1] points out that the destinations for faults should be  
able to be overridden.

In part 2, section 2, change:
"WSDL patterns specify their fault generation model using standard  
rulesets to indicate where faults may occur."
to:
"WSDL patterns specify their fault propagation models using rulesets,  
which indicate where faults may occur, and where they are propagated to  
by default (although this may be explicitly overridden; e.g., by a SOAP  
header).

In section 2.1, change:
"The fault message MUST be delivered to the same target node as the  
message it replaces."
to:
"The fault message SHOULD be delivered to the same target node as the  
message it replaces; a different destination MAY be explicitly  
nominated."

In section 2.2, change:
"The fault message MUST be delivered to the originator of the message  
which triggered it."
"
to:
"The fault message SHOULD be delivered to the originator of the message  
which triggered it; a different destination MAY be explicitly  
nominated."


1.  
http://dev.w3.org/cvsweb/%7Echeckout%7E/2002/ws/desc/issues/wsd- 
issues.html#x233

--
Mark Nottingham   Principal Technologist
Office of the CTO   BEA Systems
Received on Monday, 5 July 2004 16:47:32 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:32 GMT