Professional Documents
Culture Documents
Ashish V. Tendulkar
Directory Database integration group
(www.eusersolutions.com)
Persistent Systems Pvt. Ltd. Pune
(www.pspl.co.in)
Outline
The problem..
Why XML?
Why HTTP?
XML+HTTP = SOAP
SOAP Details
Uses of SOAP
Example
The problem..
Firewall
Implications
Industry not shifted completely to
either one
Vendor specific
Lack of interoperability
Easily extensible
Ubiquitous
SOAP Envelope
SOAP Body
<Envelope>
<Body>
<m:reverse xmlns:m='urn:strings-com:IString'>
<theString>Hello, World</theString> </m:reverse>
</Body>
</Envelope>
Example Response
200 OK
Content-Type: text/xml
Content-Length: 162
<Envelope>
<Body>
<m:reverseResponse xmlns:m='urn:strings-
com:IString'>
<result>dlroW ,olleH</result>
</m:reverseResponse>
</Body>
</Envelope>
Conclusion
SOAP is platform independent, language
neutral protocol
SOAP does not replace COM and CORBA
SOAP works in place of DCOM and IIOP
SOAP does not pose huge security risks
Supports interoperation between different
vendor specific implementations