y - Net Developer

amrameshreddy.blog.com16 CHAPTER 1 ■ INTRODUCING SERVICE-ORIENTED ARCHITECTUREramrameshreddy.blog.comSOAP MessageProtocol HeadersSOAP EnvelopeSOAP HeaderIndividual HeadersSOAP BodyMessageName and DataFigure 1-4. SOAP message structureA request-response SOAP message, as Figure 1-5 shows, essentially has two messages: oneis the request message sent to the service, and the other is a response message sent back to theclient. Although these messages are independent from each other, the request-response patternprovides automatic correlation and synchronization between the messages. This resultsin “normal” procedure call semantics to the client.SOAPSenderFaultFigure 1-5. Request-response exchange patternSyntactically a SOAP message is quite simple, but the following are a few rules you need tokeep in mind when manually writing SOAP messages:ramrameshreddyramrameshreddy• Must be encoded in XMLRequest MessageResponse Message• Must use the SOAP envelope namespace• Must use the SOAP encoding namespaceComplete SOAP messageStandard protocol (HTTP, SMTP, and so on) and SOAP header encloses payload encloses headersIndividual headers contains SOAP message name and dataXML-encoded message name and dataSOAP fault for sending exceptions using web servicesSOAPReceiver• Cannot contain a DTD reference• Cannot contain XML processing instructions