WS- Addressing <br />SOAP does not provide a standard way to specify<br /> where a message is going ? <br /> how to return a response ?<br />where to report an error ?<br />transport protocol such as HTTP , JMS can be used to define those properties .<br />
e.g. HTTP Headers<br />Host URI<br />The type of the <br />message being <br />conveyed is SOAP <br />SOAP Action<br />
WS – Addressing <br />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.<br />http://xml.coverpages.org/ws-Addressing.html<br />http://www.w3.org/TR/ws-addr-core/<br />
Asynchronous communication<br />The address of the sender of the <br />message, the addresses for return <br />reply or fault messages are given <br />current message has id “uuid:someid” <br />and it is related with another message <br />that has id “uuid:someotherid” and the <br />type of the relationship is “Reply”<br />
Dynamic endpoint addressing<br />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<br />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.<br /><From>, <ReplyTo>, <FaultTo> tags convey an “EndpointReference”<br />
More than 200 interoperability issues resolved in the Basic Profile 1.0; conventions around messaging, description and discovery
Simple SOAP Binding Profile 1.0</li></ul>— Derived from Basic Profile requirements related to serialization of an envelope and its representation in the message<br /><ul><li>Sample Applications and Testing Tools for the Basic Profile</li></ul>• Attachments Profile 1.0<br /><ul><li>Complements the Basic Profile 1.1 to add support for conveying interoperable, SOAP with Attachments (SwA) with SOAP messages</li></li></ul><li>WS- I Basic profile 1 <br /><ul><li>What is a profile?
A set of specifications at specific version levels
Guidelines and conventions for using the specifications together</li></ul> WS- I BP 1.0<br />SOAP 1.1<br />WSDL 1.1<br />UDDI 2.0<br />XML 1.0 (Second Edition)<br />XML Schema Part 1: Structures<br />XML Schema Part 2: Datatypes<br />The Secure Sockets Layer Protocol Version 3.0<br />RFC2246: The Transport Layer Security Protocol Version 1.0<br />RFC2459: Internet X.509 Public Key Infrastructure Certificate and CRL Profile<br />RFC2616: HyperText Transfer Protocol 1.1<br />RFC2818: HTTP over TLS<br />RFC2965: HTTP State Management Mechanism <br />
WS Composition <br /><ul><li>I n most of the real world scenarios it is required to interact with several services in a predefine or dynamic order.
Businesses requires to quickly adapt to customer needs and market conditions EAI and B2B interactions (through web services)
Needs to be flexible internally and externally
Without a common set of standard, each organization is left to build their own set of proprietary business protocols
Leaving little flexibility for true web services collaboration</li></li></ul><li>Web Service Composition<br />