CARVIEW |
Select Language
HTTP/2 200
date: Wed, 08 Oct 2025 06:32:11 GMT
content-type: text/html
content-encoding: gzip
last-modified: Thu, 20 Jul 2023 23:26:43 GMT
cache-control: max-age=2592000, public
expires: Fri, 07 Nov 2025 03:58:56 GMT
vary: Accept-Encoding
access-control-allow-origin: *
x-request-id: 98b2b90118cfc1cc
strict-transport-security: max-age=15552015; preload
x-frame-options: deny
x-xss-protection: 1; mode=block
cf-cache-status: HIT
age: 9194
set-cookie: __cf_bm=FML1mW3v_O5hN1sAKFoBf1O0rJ8MKRYe5mWYhcH5HNA-1759905131-1.0.1.1-EZIL9nG9nHpa_OZ9njxDk656gc8le9J1fI1w1niflpkgJqf7YkT43hEuZ8XcQeKv.9I6NIG5SisDNjII0_CYCJUEACrv_CQtXocgpi574Kg; path=/; expires=Wed, 08-Oct-25 07:02:11 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98b3997dab9ee8e0-BLR
alt-svc: h3=":443"; ma=86400
SOAP Binding Faults from James M Snell on 2002-06-10 (www-ws-desc@w3.org from June 2002)
SOAP Binding Faults
- From: James M Snell <jasnell@us.ibm.com>
- Date: Mon, 10 Jun 2002 08:21:21 -0700
- To: www-ws-desc@w3.org
- Message-ID: <OFF65E7569.85E6E1D9-ON88256BD4.00539408@boulder.ibm.com>
Just wanted to bring this up as an issue that potentially needs to be dealt with.... At a recent SOAPBuilders interop forum, we discussed the current WSDL SOAP bindings lack of being able to specify the specific fault codes that may be thrown by the various operations. For example, given the following WSDL 1.1 snippet, we can tell that a fault can be thrown, but we have no idea what specific faultcodes we should expect. <operation name="doWapSheDangDang"> <soap:operation ... /> <input>...</input> <output>...</output> <fault name="fault-name"> <soap:fault name="fault-name" use="encoded" encodingStyle="..." namespace="..." /> </fault> </operation> The soap:fault element "specifies the contents of the contents of the SOAP Fault Details element", it says absolutely nothing about the fault code. There needs to be a mechanism that allows one to specify the fault codes that may be thrown. The service would be allowed to throw fault codes other than those listed, however. Just one possible way of addressing this... (I'm sure ya'll could come up with a better one) <operation name="beBoppaLooLa"> <soap:operation ... /> <input>...</input> <output>...</output> <fault name="fault-name"> <soap:fault code="server.unauthorized" name="fault-name" use="encoded" encodingStyle="..." namespace="..." /> <soap:fault code="custom.invalidWhatchamagig" ... /> </fault> </operation> Thanks! - James M Snell/Fresno/IBM Web services architecture and strategy Internet Emerging Technologies, IBM 544.9035 TIE line 559.587.1233 Office 919.486.0077 Voice Mail jasnell@us.ibm.com Programming Web Services With SOAP, O'reilly & Associates, ISBN 0596000952 == Have I not commanded you? Be strong and courageous. Do not be terrified, do not be discouraged, for the Lord your God will be with you wherever you go. - Joshua 1:9
Received on Monday, 10 June 2002 11:21:32 UTC