WS_2015-5(SOAP).ppt

The Envelope is the top element of the XML document representing the message. The Envelope element is always the root element of a SOAP message. The Envelope element contains an optional Header element followed by a mandatory Body element. * * Two usual styles (more on this later) * The Header element is a generic container for control information It may contain any number of elements from any namespace Header blocks should contain information that influences payload processing * The Body element represents the message payload * * The SOAP specification does not define encryption for XML Web Services. This is left up to the implementer of the SOAP protocol * * SOAP simply defines the structure of the XML document used to transfer the message + possibly conventions for serializing data into XML + convention for representing method call * * * Note that this general message framework can be used to attach any valid XML-based message in the body element. In the original design of SOAP this message was intended to be serialized data organized as input/output parameter lists wrapped in method calls. If the intent is to use SOAP message bodies this way, a standard must be developed for representing generic simple and compound types in programming languages in XML. * SOAP also provides a type for representing binary data One approach for working with binary data is to use the base64 type. We can represent binary data, such as an image file, as an array of bytes in the message. The base64 type converts binary data to text using the base64-encoding algorithm of XML Schemas. There is no relationship between SOAP and base64-encoding; If we use it, our application (or implementation of SOAP for your platform) must be able to understand and work with base64-encoding. * * * Can turn it off currently scoped style using an empty string as URL () parent scoped style becomes default again SOAP Encoding: SOAP encoding is a set of serialization rules defined in section 5 o