-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Folks, here's the relevant information how WS-Addressing solved a similar issue regarding the WS-Addressing binding: The main WS-Addressing page can be found at http://www.w3.org/2002/ws/addr/ The latest published recommendations for WS-Addressing are: - WS-Addressing 1.0 - core http://www.w3.org/TR/2006/REC-ws-addr-core-20060509/ - WS-Addressing 1.0 - SOAP Biding http://www.w3.org/TR/2006/REC-ws-addr-soap-20060509/ The third document that completes the WS-Addressing 1.0 specification family of documents specifies the WSDL Binding. This document, however, is still a Candidate Recommendation: - WS-Addressing 1.0 - WSDL Binding http://www.w3.org/TR/2006/CR-ws-addr-wsdl-20060529/ The relevant information can be found in the WSDL Binding document, and in the accompanying XML Schema definition, which can be found at http://www.w3.org/2006/02/addressing/wsdl/ws-addr-wsdl.xsd Chapter 3.1 of the WSDL Binding document describes the indication of the use of WS-Addressing in a WSDL document. It defines an empty element "wsaw:UsingAdddressing" element that allows for composition with any attribute from other namespaces. In particular, the WS-Addressing 1.0 WSDL Bining document uses the "wsdl:required" attribute to mix-in the level of WS-Adddressing enfoorcement. The "wsaw:UsingAddressing" element SHOULD appear in the wsdl:binding section, but MAY instead appear in wsdl:port (WSDL 1.1) or wsdl20:endpoint if WS-Addressing compliance shall be indicated for a specific endpoint. Cheers, Michel - -- Michel <dot> Drescher <at> uk <dot> fujitsu <dot> com Fujitsu Laboratories of Europe +44 20 8606 4834 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFbxEMk0lMZTNKw4QRAiIfAJ9i7mURuiYmumoHpKes8kx6hnSL5ACgwIXK JwEE8K+90nalDZyTfOunSjo= =DPUC -----END PGP SIGNATURE-----