W3C home > Mailing lists > Public > public-ws-chor-comments@w3.org > January 2005

FW: Last Call Issue: FAULT HANDLING

From: Martin Chapman <martin.chapman@oracle.com>
Date: Mon, 10 Jan 2005 14:50:52 -0000
To: <public-ws-chor-comments@w3.org>
Message-ID: <00b101c4f723$c9aeab00$0901a8c0@ie.oracle.com>
 

-----Original Message-----
From: public-ws-chor-request@w3.org
[mailto:public-ws-chor-request@w3.org] On Behalf Of Gary Brown
Sent: 05 January 2005 14:25
To: public-ws-chor@w3.org
Subject: Last Call Issue: FAULT HANDLING


The current spec defines WSDL1.1 faults using the InformationType to
relate to the appropriate WSDL Message Type. However, if an operation
has multiple faults, each with the same Message Type, then the only
thing that distinguishes them is the fault name. 

However, the 'interaction' syntax does not support specifying a name
associated with the "respond" exchange, when it is receiving a fault -
it only specifies the Information Type, which in turn only links to the
WSDL message type. The actual fault name is not referenced anywhere.

For consistency across WSDL1.1 and WSDL2, perhaps the InformationType
could refer to the actual type structure (which would be a change
related to the WSDL2 support in the current spec), and then the
'exchange' is changed so that when it is used to receive a fault (i.e.
an ExceptionType), the name field is the actual fault name - which could
map onto WSDL1.1 and WSDL2.

Regards

Gary and Steve
Received on Monday, 10 January 2005 14:50:16 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:20:10 GMT