cr9: wsa:Action for undefined faults

I had an action to provide spec text for the preferred option (3):

I propose we add to Section 5 of the SOAP Binding, right after the text:

  The [action] property below designates WS-Addressing fault messages:

    http://www.w3.org/@@@@/@@/addressing/fault

This paragraph:

  The [action] property value below MAY be used to designate SOAP fault
  messages (e.g. mustUnderstand faults):

    http://www.w3.org/@@@@/@@/addressing/soap/fault

That's it!

-----Original Message-----
From: public-ws-addressing-comments-request@w3.org
[mailto:public-ws-addressing-comments-request@w3.org] On Behalf Of
Jonathan Marsh
Sent: Monday, October 17, 2005 2:35 PM
To: public-ws-addressing-comments@w3.org
Cc: peter.hendry@capeclear.com; tom@coastin.com
Subject: [New Issue] FW: wsa:Action for undefined faults


Please add this issue to the CR issues list.

Several options have emerged so far:

Option 0: Do nothing - describing this level of fault oversteps the
          bounds of WS-Addressing.  Perhaps note in the spec that\
          such action values are explicitly not defined.
Option 1: Reuse http://www.w3.org/@@@@/@@/addressing/fault.
Option 2: Define a new action URI for soap faults (e.g. /soap/fault).

-----Original Message-----
From: public-ws-addressing-request@w3.org
[mailto:public-ws-addressing-request@w3.org] On Behalf Of Jonathan Marsh
Sent: Friday, October 14, 2005 2:21 PM
To: Pete Hendry; tom@coastin.com
Cc: public-ws-addressing@w3.org
Subject: RE: wsa:Action for undefined faults


In the submission a static fault URI was used for all faults (including
general SOAP faults).  Seems like we lost that when we changed how fault
actions are determined.  I propose the simplest fix, that we also state
that SOAP faults use the action we've already defined:
http://www.w3.org/@@@@/@@/addressing/fault.

P.S. Is this on the issues list?  I didn't see it there...

> -----Original Message-----
> From: public-ws-addressing-request@w3.org [mailto:public-ws-
> addressing-request@w3.org] On Behalf Of Pete Hendry
> Sent: Saturday, October 01, 2005 1:53 AM
> To: tom@coastin.com
> Cc: public-ws-addressing@w3.org
> Subject: Re: wsa:Action for undefined faults
> 
> 
> 
> It doesn't cover general SOAP level faults (bad request, etc.). What
> is
> used for them?
> 
> Pete
> 
> Tom Rutt wrote:
> 
> > Pete Hendry wrote:
> >
> >>
> >> The definition of wsa:Action says
> >>
> >>    /wsa:Action
> >>    This REQUIRED element of type xs:anyURI conveys the [action]
> >> property.
> >>
> >> I was wondering what value Action takes where a general SOAP fault
> is
> >> encountered such as malformed XML? This will not match any fault
> >> defined in the WSDL. Also, what value does it take when of the the
> >> WSA faults occur? I assume REQUIRED means on both request and
> >> response even if the response is a fault?
> >>
> >> In section 3.2 it says
> >>
> >>    Populate the reply message's message addressing properties
> >>       o [destination]: ...
> >>       o [relationship]: ...
> >>       o [reference parameters]: ...
> >>
> >> Missing from this is [action]? The examples that follow should
> >> wsa:Action in each case.
> >>
> >> Does there need to be general fault action URIs such as
> >
> >
> > One is defined in the Soap binding
> > spec:http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/ws-addr-
> soap.html?content-type=text/html;%20charset=utf-8
> >
> >
> > In section 5 the following paragraph defines generic URI
> > "
> >
> > The [action] property below designates WS-Addressing fault messages:
> >
> > http://www.w3.org/@@@@/@@/addressing/fault
> > "
> >
> > Tom Rutt
> >
> >
> >
> >>
> >>    .../fault/addressing
> >>    .../fault/unspecified
> >>
> >> I am coming up against this problem in implementing the spec.
> >>
> >> Pete
> >>
> >
> >

Received on Tuesday, 25 October 2005 22:41:17 UTC