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

RE: i67 and i68 proposal for WSDL doc

From: David Orchard <dorchard@bea.com>
Date: Thu, 19 Jan 2006 14:39:14 -0800
Message-ID: <E16EB59B8AEDF445B644617E3C1B3C9C632883@repbex01.amer.bea.com>
To: "WS-Addressing" <public-ws-addressing@w3.org>
Note that response message versus outbound message vs output appear to
be inconsistent.

 

3.4 Non-anonymous indicated

This section describes the Message Exchange Patterns and binding changes
when WS-Addressing is indicated.

 

3.4.1 SOAP 1.1/HTTP binding

WS-Addressing changes the SOAP 1.1/HTTP binding used when the value of
the response endpoint EPR contains an address that is intended to be
used as an address by a binding (for example, a value other than the
WS-Addressing anonymous URI).  In this case, the receiver of a message
MUST use a binding that supports not returning a SOAP envelope in the
HTTP response, such as [URI for binding doc].  If the value of the
response endpoint EPR contains an address that is intended to be used as
an address by a binding (for example, a value other than the
WS-Addressing anonymous URI), then outbound message MUST be sent using a
separate connection and using the address value specified by response
endpoint.  

 

3.4.2 SOAP 1.2 binding

When the value of the response endpoint EPR contains the anonymous
address and the request is the request part of a SOAP request-response
MEP [soap 1.2 adjuncts ref], then the response must be the response part
the same SOAP request-response MEP [soap 1.2 adjuncts ref].  When the
value of the response endpoint EPR contains a value that is intended to
be used as an address by a binding (for example, a value other than the
WS-Addressing anonymous URI) then any response message is not part of
the mep that the request message is in.

 

 

________________________________

From: David Orchard 
Sent: Thursday, January 19, 2006 2:18 PM
To: WS-Addressing
Subject: RE: i67 and i68 proposal for WSDL doc

 

3.4 Non-anonymous indicated

This section describes the Message Exchange Patterns and binding changes
when WS-Addressing is indicated.

 

3.4.1 SOAP 1.1/HTTP binding

WS-Addressing changes the SOAP 1.1/HTTP binding used when the value of
the response endpoint EPR contains an address that is different that is
intended to be used as an address by a binding (for example, a value
other than the WS-Addressing anonymous URI).  In this case, the receiver
of a message MUST use a binding that supports not returning a SOAP
envelope in the HTTP response, such as [URI for binding doc].  If the
value of the response endpoint EPR contains an address that is different
than the anonymous URI, the outbound message MUST be sent using a
separate connection and using the address value specified by response
endpoint.  

3.4.2 SOAP 1.2 binding

When the value of the response endpoint EPR contains the anonymous
address, then the request and any response message are part of a single
SOAP request-response MEP [soap 1.2 adjuncts ref].  When the value of
the response endpoint EPR contains a value that is intended to be used
as an address by a binding (for example, a value other than the
WS-Addressing anonymous URI) then any response message is not part of
the mep that the request message is in.

 

 

________________________________

From: public-ws-addressing-request@w3.org
[mailto:public-ws-addressing-request@w3.org] On Behalf Of David Orchard
Sent: Friday, January 13, 2006 12:52 PM
To: WS-Addressing
Subject: i68 and i69 proposal for WSDL doc

 

V.Real

 

Here's a proposal for how the WSDL binding doc would refer to external
documents.  I had to really really squint hard to convince myself that
"Indicating use of WS-Addressing" is the right section for soap
binding/mep changes..  I mean, really really really hard.  

 

3.4 Non-anonymous indicated

This section describes the Message Exchange Patterns and binding changes
when WS-Addressing is indicated.

 

3.4.1 SOAP 1.1/HTTP binding

WS-Addressing changes the SOAP 1.1/HTTP binding used when the value of
the response endpoint EPR contains an address that is different than the
anonymous URI.  In this case, the receiver of a message MUST use a
binding that supports not returning a SOAP envelope in the HTTP
response, such as [URI for binding doc].  If the value of the response
endpoint EPR contains an address that is different than the anonymous
URI, the outbound message MUST be sent using a separate connection using
the address value of the specified by appropriate response endpoint.
The outbound message MAY use a binding that supports not returning a
SOAP envelope in the HTTP response, such as [URI for binding doc]

 

3.4.2 SOAP 1.2 binding

When the value of the response endpoint EPR contains the anonymous
address, then the inbound and any outbound message are part of a single
SOAP request-response MEP [soap 1.2 adjuncts ref].  When the value of
the response endpoint EPR does not contain the anonymous address, then
any outbound message is not part of the mep that the inbound message is
in.

 

 
Received on Thursday, 19 January 2006 22:39:45 GMT

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