- From: Mark Nottingham <mark.nottingham@bea.com>
- Date: Fri, 30 Sep 2005 20:35:55 -0700
- To: W3C WS-Addressing Public List <public-ws-addressing@w3.org>
The following were the options on the screen during the F2F for these issues: option 1: The [destination] property is taken from the endpoint or port address - derived address (WSDL 2.0) or the applicable WSDL 1.1 extension (for SOAP it is taken from soap:address/@location). wsa:ReferenceParameters can be a child element of a wsdl20 endpoint or a wsdl 11 port. option 2: a) Allow a wsa:EndpointReference element to be included as a child of wsdl20:endpoint or wsdl11:port. b) When a wsa:EndpointReference element is present as a child of a wsdl20:endpoint/wsdl11:port the usual WS-Addressing/binding rules apply [destination]=wsa:EndpointReference/wsa:Address. Semantics of WSDL- related metadata (e.g., WSDL namespace metadata, wsdl-related MAPs) are undefined in such EPRs. c) When there is no wsa:EndpointReference child element, the [destination] property is taken from the endpoint or port address - endpoint/@address (WSDL 2.0) or the applicable WSDL 1.1 extension (for SOAP it is taken from soap:address/@location). d) If there is both a wsa:EndpointReference and an endpoint/port address then they must have the same value. option 3: option 2 - d -- Mark Nottingham Principal Technologist Office of the CTO BEA Systems
Received on Saturday, 1 October 2005 03:36:11 UTC