R4R provide basic SOAP Tutorials concept with SOAP Examples .Through R4R you can develop SOAP programming concept. R4R provide SOAP Interview Questions with answers.R4R provide SOAP Languages study materials in easy way.
SOAP stands for Simple Object Access Protocol. SOAP is a communication protocol. SOAP is a simple XML-based protocol to let applications exchange information over HTTP. SOAP was originally developed by Microsoft, IBM, Develop Mentor and User land Software and was then submitted to the Internet Engineering Task Force (IETF), who eventually made it an official recommendation.
SOAP (Simple Object Access Protocol) is a simple solution for interaction of different applications built in different languages and running on different platforms as it uses HTTP as its transport and XML as its payload for sending and receiving message
Simple Object Access Protocol (SOAP) provides access to remote objects.
The following components of a SOAP communications architecture are
The SOAP object model consists of three main objects
The Envelope must be the first element in a SOAP message. It identifies an XML document as being a SOAP message and encapsulates all the other parts of a message. Envelope contains the version information about the message, and it identifies the rules used by the application to serialize data. Both the version and encoding rules are represented as namespace URIs in the Envelope. The Envelope must be the first element in a SOAP message. It identifies an XML document as being a SOAP message and encapsulates all the other parts of a message.
Envelope contains the version information about the message, and it identifies the rules used by the application to serialize data. Both the version and encoding rules are represented as namespace URIs in the Envelope. A SOAP message is an XML document that consists of a fixed SOAP envelope, an optional SOAP header, and a mandatory SOAP body as the following: The Envelope is the top element of the XML document representing the message.
SOAP message contain header entries specifying nodes that perform authorization-processing, encryption, persistence of state, business logic processing, in addition to defining transaction nodes like the one described. With Headers SOAP is able to make a modular, extensible packaging mode The SOAP Body
RPC-based view of the SOAP message presented earlier. Only the body portions of the SOAP request and response envelopes are shown.
<SOAP-ENV:Body>
<m:GetLastTradePrice xmlns:m=
"URI"
>
<symbol>DEF</Symbol>
</m:GetLastTradePrice>
</SOAP-ENV:Body>
The SOAP processing model describes a distributed processing model, its participants, the SOAP nodes and how a SOAP receiver processes a SOAP message. The following SOAP nodes are defined
- SOAP sender- A SOAP node that transmits a SOAP message.
- SOAP receiver- A SOAP node that accepts a SOAP message.
- SOAP message path- The set of SOAP nodes through which a single SOAP message passes. Initial SOAP sender (Originator): The SOAP sender that originates a SOAP message at the starting point of a SOAP message path.
- SOAP intermediary- A SOAP intermediary is both a SOAP receiver and a SOAP sender and is target able from within a SOAP message. It processes the SOAP header blocks targeted at it and acts to forward a SOAP message towards an ultimate SOAP receiver.
- Ultimate SOAP receiver- The SOAP receiver that is a final destination of a SOAP message. It is responsible for processing the contents of the SOAP body and any SOAP header blocks targeted at it. In some circumstances,
- SOAP can be considerably slower than competing middleware technologies such as CORBA because of the verbose XML format.
- When relying on HTTP as a transport protocol and not using WS-Addressing or an ESB, the roles of the interacting parties are fixed.
- When relying on HTTP as a transport protocol, a firewall designed to only allow web browsing is forced to perform more detailed (and thus more costly) analysis of the HTTP packages.