Re: FW: New Issue: SOAP Binding CR ([Details] for wsa:ActionMismatch Subsubcode)

I think this is in line with the consolidation of the fault elements
that we did in Boston just prior to CR, so +1.

In particular, +1 to "Subject to negative impact on our progress out of
CR, of course ;-)."

Jonathan Marsh wrote:

>
>         *Arun pointed out that there is redundant information in the
>         fault detail for wsa:ActionMismatch.  We already know the
>         problem lies with a header named wsa:Action so
>         <wsa:ProblemHeaderQName> isn't necessary.  We already have a
>         way to communicate the content of the problem header in
>         <wsa:ProblemAction>, so <wsa:ProblemHeader> isn't necessary. 
>         The only information that isn't redundant is the value of
>         SOAPAction.  *
>
>
>         *This redundancy represents needless complication.  I propose
>         we keep <wsa:ProblemHeader> and <wsa:ProblemHeaderQName> for
>         consistency and to enable "dumber" conveyance of this
>         information, and strip down <wsa:ProblemAction>.  (I fix
>         another problem as well - that
>         was:ProblemAction/wsa:SoapAction doesn't seem to be extensible
>         which is inconsistent with other elements we define.)*
>
>
>         *I propose we replace the following sections:*
>
>
>         *5.3.4 Problem Action*
>
> The following describes the <wsa:ProblemAction> element:
>
> */wsa:ProblemAction/wsa:Action *
>
> An optional element that provides the [action] that caused the problem.
>
> */wsa:ProblemAction/wsa:SoapAction *
>
> An optional element that provides the SOAPAction IRI that caused the
> problem.
>
> */wsa:ProblemAction/{any} *
>
> Optional extensibility elements that do not affect processing.
>
> */wsa:ProblemAction/@{any} *
>
> Optional extensibility attributes that do not affect processing.
>
> ...
>
>
>           */5.4.1.6 wsa:ActionMismatch/*
>
> Specifies that the [action] and SOAPAction for the message did not
> match, [Details] MAY contain a <wsa:ProblemAction> element in addition
> to the <wsa:ProblemHeader> element or <wsa:ProblemHeaderQName> element.
>
>  
>
>
>         *With:*
>
>
>         *5.3.4 Problem SOAPAction*
>
> The following describes the <wsa:ProblemSOAPAction> element:
>
> */wsa:ProblemSOAPAction *
>
> An optional element that provides the SOAPAction IRI that caused the
> problem.
>
> */wsa:ProblemSOAPAction/{any} *
>
> Optional extensibility elements that do not affect processing.
>
> */wsa:ProblemSOAPAction/@{any} *
>
> Optional extensibility attributes that do not affect processing.
>
> ...
>
>
>           */5.4.1.6 wsa:ActionMismatch/*
>
> Specifies that the [action] and SOAPAction for the message did not
> match, [Details] MAY contain a <wsa:ProblemSOAPAction> element in
> addition to the <wsa:ProblemHeader> element or
> <wsa:ProblemHeaderQName> element.
>
>  
>
> Subject to negative impact on our progress out of CR, of course ;-).
>
>  
>
> --  Jonathan Marsh  --  jmarsh@microsoft.com
> <mailto:jmarsh@microsoft.com>  -- 
> http://spaces.msn.com/members/auburnmarshes/  --
>
>  
>
>  
>
>  
>
> -----Original Message-----
> From: public-ws-addressing-comments-request@w3.org
> [mailto:public-ws-addressing-comments-request@w3.org] On Behalf Of
> Arun Gupta
> Sent: Friday, August 26, 2005 11:27 AM
> To: public-ws-addressing-comments@w3.org
> Subject: New Issue: SOAP Binding CR ([Details] for wsa:ActionMismatch
> Subsubcode)
>
>  
>
>  
>
> In SOAP Binding, Candidate Recommendation, section 5.4.1.6 [1],
>
> [Details] should contain <wsa:ProblemAction> instead of
>
> <wsa:ProblemHeader> or <wsa:ProblemHeaderQName> since that is more
>
> relevant information regarding the fault.
>
>  
>
> [1]
>
> http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/ws-addr-soap.html#invalidmapfault
>
>  
>
> -- 
>
> got Web Services ?
>
> Download Java Web Services Developer Pack from
>
> http://java.sun.com/webservices
>
>  
>