Download Web services for a Software Development Platform

 accepted by the people and this version influence several open source interoperable
implementations. WS-I.org adopted it as part of its basic profile. In May 2000 the W3C took the
SOAP 1.1 and it in charge to preserve standardized new generation.
As we know SOAP is the fundamental messaging framework for Web services. With SOAP the
services could be provided by a loosely coupled infrastructure, and users could flexibly use
different implementation technologies and network transport protocols. SOAP provides the
following four main capabilities:
“
‹ A standardized message structure based on the XML Infoset.
‹ A processing model that describes how a service should process the message.
‹ A mechanism to bind SOAP message to different network transport protocols.
‹ A way to attach non-XML encoded information to SOAP message.
” (Weerawarana et al. 2005, p.63) [3]
SOAP defines an extensible message handle mechanism that scopes and structures the message
enveloping model and the message exchange between Web services. A common SOAP was
documented in XML form with three key parts: an envelope, a header, and a body. Usually, the
envelope is the root element of the SOAP massage; it contains zero or more headers and at least
one body. The header in an optional part of SOAP massage and it is a generic mechanism for
adding extensible features to SOAP. The child element of the header are called head block. SOAP
defines several well-known attributes that you can use to indicate who should deal with a header
block and whether processing of it is optional or mandatory. The mandatory body element always
is the last child element of the envelope, it include the actual payload message content. SOAP
defines when a message does not have any built-in header blocks and only one payload, which is
the Fault element used for reporting errors. Table 2.1 is an SOAP message example:
<?xml version=’1.0’ encoding=’UTF‐8’ ?> <soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap‐envelope> <soapenv:Header> … (Header Blocks) </soapenv:Header> <soapenv:Body> … (Body sub‐elements) </soapenv:Body> </soapenv:Envelope> Table 2. 1 SOAP Message XML Example
SOAP is designed to provide an independent, abstract communication protocol capable of
bridging, or connecting, two or more businesses or two or more remote business sites. “A SOAP
message is the basic unit of communication between SOAP nodes. A SOAP node is an
implementation of the processing rules described within the SOAP specification that can transmit,
receive, process, or relay a SOAP message.” (Weerawarana et al. 2005, p.65) [3] SOAP nodes
could send and receive SOAP messages. When a SOAP node transmit massage, it is called a
SOAP sender if it receives a message, it is called s SOAP receiver; some of SOAP node could
9