W3C home > Mailing lists > Public > public-ws-addressing@w3.org > January 2005

Re: i022: Relationship to the SOAP Binding Framework: a SOAP Request MEP and OneWay HTTP Binding

From: Marc Hadley <Marc.Hadley@Sun.COM>
Date: Thu, 06 Jan 2005 17:45:13 -0500
To: David Orchard <dorchard@bea.com>
Cc: public-ws-addressing@w3.org
Message-id: <A0956334-6034-11D9-AE5B-000A95BC8D92@Sun.COM>

On Dec 17, 2004, at 5:06 PM, David Orchard wrote:
>
> Some of the tricky areas that I thought I'd call out:
>
> - There is an optional binding specific response in the one-way MEP.
>
> - Relationship to media type.  I think this be covered by the soap 
> media-type, but I'm not 100% sure.  I'm not sure about the case of 
> whether a soap+xml is good enough for this mep+binding, I sure hope so 
> though.
>
> - Webmethod support: I said POST only
>
> - The identification of the mep in use can't be gleaned from the 
> information in the binding, unlike the SOAP HTTP Binding
>
> - Streaming: I consistently said that requesting SOAP nodes must avoid 
> deadlock by accepting binding-specific response messages
>
> - I removed "receiving" state from the next state tables.
>
> - SOAP faults cannot come back over the http response.  For 
> request-response bound to 2 http requests, life sucks.
>
I'm confused, the doc says:

"2.4 Fault Handling

During the operation of the Request MEP, the  participating SOAP nodes 
may generate SOAP faults.

If a SOAP fault is generated by the recieiving SOAP node  while it is 
in the "Receiving" state, the SOAP  fault is made available in 
http://www.w3.org/2003/05/soap/mep/OutboundMessage and the  state 
machine transitions to the "Fail" state."

Section "3.5.2.2 Receiving" allows for a SOAP message in the response 
HTTP entity body. Doesn't this allow a fault to come back over the http 
response like the WSDL robust-in-only MEP ?

> - The binding can allow an empty body, especially for cases where the 
> action is sufficient.
>
An empty HTTP entity body, not an empty SOAP body - right ?

Marc.

> - I kept the HTTP status code at 200
>
>  
>
> I would also like to mention that I found this exercise very 
> informative.  I think that SOAP has provided an excellent framework 
> for creating interoperable meps and bindings as it forced me to think 
> about many hard issues.
>
>  
>
> Cheers,
>
> Dave
>
>  
>
>  
> <ws-addr-soapadjuncts.xml><WS-Addressing-SOAP-Adjuncts.html>
---
Marc Hadley <marc.hadley at sun.com>
Web Technologies and Standards, Sun Microsystems.
Received on Thursday, 6 January 2005 22:45:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:35:01 GMT