W3C home > Mailing lists > Public > public-ws-desc-comments@w3.org > September 2004

Re: binding/operation/infault|outfault?

From: Roberto Chinnici <Roberto.Chinnici@Sun.COM>
Date: Tue, 07 Sep 2004 11:39:40 -0700
To: Bob Cunnings <cunnings@lectrosonics.com>
Cc: public-ws-desc-comments@w3.org
Message-id: <413E006C.80505@sun.com>

I believe they were removed when we lifted faults to the interface level
and introduced Interface Fault components. Since faults are now shared
by multiple operations, they can only be bound once in an interface
by using a Binding Fault component.

For example, it's not possible for a single fault, used by three
different operations, to result in SOAP faults with different fault
codes depending on which operation was being invoked when the fault
was raised. I vaguely remember the WG discussing this case at
the January 2004 F2F hosted by Sonic.

If there is a genuine need for allowing different operations in the
same interface to bind the same fault differently, we may want
to (re-)introduce a Binding Fault Reference component. So please
tell us more about your use case.


Bob Cunnings wrote:
> Hello,
> In the LC version of Part 1 [1], <infault> and <outfault> element
> information items are no longer listed among the children of the XML
> representation of the Binding Operation component.
> Is there a reason why they fell out? I can't find any reference to
> changes to that area since the removal of
> binding/operation/infault|outfault@messageReference in the 2004/12/04
> teleconference minutes. [2]
> What I would like to be able to do is specify a soap:module [3] in a
> binding for an output fault message for specific operations.
> Thanks,
> RC
> [1]
> http://www.w3.org/TR/2004/WD-wsdl20-20040803/#Binding_Operation_XMLRep
> [2] http://lists.w3.org/Archives/Public/www-ws-desc/2003Dec/0017.html
> [3] http://www.w3.org/TR/2004/WD-wsdl20-bindings-20040803/
Received on Tuesday, 7 September 2004 18:36:47 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:31:00 UTC