SOAP

Learn about SOAP

SOAP

simple object access protocol

what is soap

the core underlying middleware protocol for most web services

container

a process whose main goal is to host components

container and component interaction

the container provides the lifecycle services and the components provide the user functionality

containers in web services

they are typically a web server that can redirect requests to other code

SOAP vs XML RPC

SOAP also uses XML to generate messages passed to endpoints, but doesn’t mandate a single schema or a single syntax

what does a soap interaction consist of 1

wire protocol - how data is passed over the network (http)

what does a soap interaction consist of 2

marshalling - converting values into a wire representation suitable for transfer (xml)

what does a soap interaction consist of 3

endpoint addresses - the mechanism for identifying where data should be streamed to (urls)

how is soap message-based

the client sends a message and may later receive a result message back. fast and non blocking

programming view on asynchonicity

makes SOAP more like MOM than DO or RPC, harder for the programmer to control

current SOAP abstraction

it sits on top of HTTP as its transport protocol. note that there is no requirement that SOAP has to use HTTP

significant things in SOAP requests and responses 1

extensive use of XML namespaces

significant things in SOAP requests and responses 2

the main part of the request format is user-specified

significant things in SOAP requests and responses 3

the forms of requests and responses are the same - an envelope containing message body and the payload in a user-defined XML format

significant things in SOAP requests and responses 4

it is just xml documents, way simpler than most other middlewares that have been developed