WS- Addressing SOAP does not provide a standard way to specify where a message is going ? how to return a response ? where to report an error ? transport protocol such as HTTP , JMS can be used to define those properties .
e.g. HTTP Headers Host URI The type of the message being conveyed is SOAP SOAP Action
WS – Addressing WS-Addressing was originally authored by Microsoft, IBM, BEA, Sun, and SAP and submitted to W3C for standardization. The W3C WS-Addressing Working Group has refined and augmented the specification in the process of standardization. http://xml.coverpages.org/ws-Addressing.html http://www.w3.org/TR/ws-addr-core/
Asynchronous communication The address of the sender of the message, the addresses for return reply or fault messages are given current message has id “uuid:someid” and it is related with another message that has id “uuid:someotherid” and the type of the relationship is “Reply”
Dynamic endpoint addressing Endpoint is any addressable resource to which SOAP message can be sent (Web Service client or application, a SOAP router or any SOAP aware entity The most logical way to include endpoints is to use WSDL “Service” element, however WSDL does not allow extensibility of this element, therefore EndpointReference is defined. <From>, <ReplyTo>, <FaultTo> tags convey an “EndpointReference”
— Derived from Basic Profile requirements related to serialization of an envelope and its representation in the message
Sample Applications and Testing Tools for the Basic Profile
• Attachments Profile 1.0
Complements the Basic Profile 1.1 to add support for conveying interoperable, SOAP with Attachments (SwA) with SOAP messages
WS- I Basic profile 1
What is a profile?
A set of specifications at specific version levels
Guidelines and conventions for using the specifications together
WS- I BP 1.0 SOAP 1.1 WSDL 1.1 UDDI 2.0 XML 1.0 (Second Edition) XML Schema Part 1: Structures XML Schema Part 2: Datatypes The Secure Sockets Layer Protocol Version 3.0 RFC2246: The Transport Layer Security Protocol Version 1.0 RFC2459: Internet X.509 Public Key Infrastructure Certificate and CRL Profile RFC2616: HyperText Transfer Protocol 1.1 RFC2818: HTTP over TLS RFC2965: HTTP State Management Mechanism