W3C home > Mailing lists > Public > xml-dist-app@w3.org > October 2001

Intent of SOAP fault code extensibility

From: Paul Gibbons <pgibbons@earthconnect.com>
Date: Mon, 8 Oct 2001 16:02:52 -0700
Message-ID: <07B09B78AB5404489553DE23BFA83EEC0226BA@ec-exchange-01.corp.earthconnect.com>
To: <xml-dist-app@w3.org>
Looking through the archives of this list I find that the issues arising

from the extensibility of SOAP fault codes as described in section 4.4.1

have been raised but not answered.

It is not clear to me whether the extension mechanism is intended for
in future versions of the SOAP specification, in related specifications
by service authors.

Although the SOAP spec recommends doing so, it would seem to be a bad
for me to create my own fault code using the SOAP envelope namespace
I don't control it.

Since the fault codes are XML qualified names I have to resort to
comparisons if I just care about Client faults and not sub codes such as


If I go ahead and define codes for my service such as
using namespace http://paul.earthconnect.com/fault-codes am I violating
spirit of the spec?

Can somebody who was involved in creating this section of the spec
on the intent so I don't head off into left field? 

I realize I could communicate my own code in the fault detail (except
header faults) but it's not clear to me that I shouldn't use the fault
directly (of course it's equally unclear that I should, which is why I'm

raising this issue).


Paul John Gibbons
Software Architect
EarthConnect Corporation
(206) 417 8000
NOTICE: This e-mail message is the property of EarthConnect Corporation.
The contents of this message and any attachments are confidential and
are protected by law as confidential.  If you are not the intended
recipient of this message, please forward a copy to the sender and
delete the message and its attachments from your computer.
Received on Monday, 8 October 2001 19:03:59 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 22:01:16 UTC