W3C home > Mailing lists > Public > www-tag@w3.org > March 2006

Re: SOAP & Web arch

From: Mark Baker <distobj@acm.org>
Date: Thu, 30 Mar 2006 14:28:27 -0500
Message-ID: <c70bc85d0603301128l67eaef57h27ad4b8cc6451460@mail.gmail.com>
To: "David Orchard" <dorchard@bea.com>
Cc: www-tag@w3.org

Hey Dave,

On 3/30/06, David Orchard <dorchard@bea.com> wrote:
> Does this apply to all SOAP meps?  In particular, does the
> immediatedestination get set to the address value for all meps, or just
> when HTTP is known to be the binding?  I'll yet again observe that the
> SOAP 1.2 request-response MEP tries to abstract away which protocol is
> in effect, so it breaks the MEP abstraction to talk about
> immediatedestination when HTTP is the protocol.

Hmm, I don't see how that follows.  I agree that the Req/Resp MEP is
"protocol independent", but it does expose the ImmediateDestination
property which is not HTTP specific at all AFAICT.  It only "meets"
HTTP in the HTTP binding where the MEP is instantiated and
ImmediateDestination is bound to the HTTP Request-URI.

> Note that we added something like this into WSDL 2.0 " The SOAP
> "http://www.w3.org/2003/05/soap/mep/ImmediateDestination" property takes
> the value of the WSDL {address} property of the Endpoint component."

Interesting, though I'm not sure how that impacts the message.

> So something like the following in WS-A SOAP binding would satisfy you?
> I'm not that I'm saying that I agree with it, just making sure it's
> crystal clear.
> <<current text>>
> 3.4 Binding Message Addressing Properties
> When a message is to be addressed to an endpoint, the XML Infoset
> representation of each message addressing property that has been
> assigned a value is inserted into the message as a SOAP header block
> subject to the following additional constraints:
> <</current text>>
> <<new text>>
> When using HTTP, the address value is also copied to the HTTP
> request-uri field.  In SOAP 1.2, this means the SOAP
> "http://www.w3.org/2003/05/soap/mep/ImmediateDestination" property takes
> the address value when the HTTP binding is used.
> <</new text>>

That would be an HTTP-specific fix, sure.  But a generic fix would be
to simply say that the WSA address property should also(*) be bound to
the ImmediateDestination SOAP property.

This would, of course, require that all MEPs supported by WSA have an
ImmediateDestination property with these semantics.  That's certainly
the case for the two defined by SOAP 1.2, and I would expect it to be
the case that other MEPs would have something similar .. but I suppose
it might have a different name.  I'm not familiar with any other MEPs
though (or at least none come immediately to mind).

Either way would work for me.


(*) I presume the WG would want to keep the wsa:To header. 8-)

Mark Baker.  Ottawa, Ontario, CANADA.       http://www.markbaker.ca
Received on Thursday, 30 March 2006 19:28:38 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:32:48 UTC