＋设为首页 ＋添加到收藏夹
(c) 2002-2004 bea systems inc., international business machines corporation, microsoft corporation, inc, sap ag, and sun microsystems. all rights reserved.
permission to copy and display the ws-addressing specification (the "specification"), in any medium without fee or royalty is hereby granted, provided that you include the following on all copies of the specification that you make:
1. a link or url to the specification at this location.
2. the copyright notice as shown in the specification.
bea systems, ibm, microsoft, sap, and sun (collectively, the "authors") each agree to grant you a license, under royalty-free and otherwise reasonable, non-discriminatory terms and conditions, to their respective essential patent claims that they deem necessary to implement the ws-addressing specification.
the specification is provided "as is," and the authors make no representations or warranties, express or implied, including, but not limited to, warranties of merchantability, fitness for a particular purpose, non-infringement, or title; that the contents of the specification are suitable for any purpose; nor that the implementation of such contents will not infringe any third party patents, copyrights, trademarks or other rights.
the authors will not be liable for any direct, indirect, special, incidental or consequential damages arising out of or relating to any use or distribution of the specifications.
the name and trademarks of the authors may not be used in any manner, including advertising or publicity pertaining to the specifications or their contents without specific, written prior permission. title to copyright in the specifications will at all times remain with the authors.
no other rights are granted by implication, estoppel or otherwise.
abstractws-addressing provides transport-neutral mechanisms to address web services and messages. specifically, this specification defines xml [xml 1.0, xml namespaces] elements to identify web service endpoints and to secure end-to-end endpoint identification in messages. this specification enables messaging systems to support message transmission through networks that include processing nodes such as endpoint managers, firewalls, and gateways in a transport-neutral manner.
statusws-addressing and related specifications are provided as-is and for review and evaluation only. bea, ibm, microsoft, sap, and sun make no warrantees or representations regarding the specifications in any manner whatsoever.
table of contents1. introduction
1.1 notational conventions
1.2 namespaces
2. endpoint references
2.1 information model for endpoint references
2.2 endpoint reference xml infoset representation
2.3 binding endpoint references
2.4 endpoint reference comparison
3. message information headers
3.1 message information headers xml infoset representation
3.2 formulating a reply message
3.3 associating action with wsdl operations
3.3.1 explicit association
3.3.2 default action pattern
4. faults
4.1 invalid message information header
4.2 message information header required
4.3 destination unreachable
4.4 action not supported
4.5 endpoint unavailable
5. security considerations
6. acknowledgements
7. references
1. introductionweb services addressing (ws-addressing) defines two interoperable constructs that convey information that is typically provided by transport protocols and messaging systems. these constructs normalize this underlying information into a uniform format that can be processed independently of transport or application. the two constructs are endpoint references and message information headers.
a web service endpoint is a (referenceable) entity, processor, or resource where web service messages can be targeted. endpoint references convey the information needed to identify/reference a web service endpoint, and may be used in several different ways: endpoint references are suitable for conveying the information needed to access a web service endpoint, but are also used to provide addresses for individual messages sent to and from web services. to deal with this last usage case this specification defines a family of message information headers that allows uniform addressing of messages independent of underlying transport. these message information headers convey end-to-end message characteristics including addressing for source and destination endpoints as well as message identity.
both of these constructs are designed to be extensible and re-usable so that other specifications can build on and leverage endpoint references and message information headers.
the following example illustrates the use of these mechanisms in a soap 1.2 message being sent from http://business456.example/client1 to http://fabrikam123.example/purchasing:
... 下一页