Dec 7, 2007. SOAP vs REST. Can you read this? If not, please sit closer. Thank you. XML RPC (1998). Request <?xml version="1.0"?> < methodCall > < methodName > doSomeWork </ methodName > < params > < param > <value>< int >40</ int ></value> </ param > < param >
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
Can you read this? If not, please sit closer. Thank you.
<e:Book> <title>My Life and Work</title> <author href="#Person-1"/></e:Book>
<e:Person id="Person-1"> <name>Henry Ford</name> <address href="#Address-2"/></e:Person>
<e:Address id="Address-2"> <email>mailto:[email protected]</email> <web>http://www.henryford.com</web></e:Address>
<SOAP-ENC:Array SOAP-ENC:arrayType="xsd:string[,]"> <SOAP-ENC:Array href="#array-1" SOAP-ENC:position=""/></SOAP-ENC:Array>
<SOAP-ENC:Array id="array-1" SOAP-ENC:arrayType="xsd:string[10,10]"> <item SOAP-ENC:position="[2,2]">Third row, third col</item> <item SOAP-ENC:position="[7,2]">Eighth row, third col</item></SOAP-ENC:Array>
Namespace does not
have to be the same
as the parameter values
Argument elements don’t
even have a namespace
Lets you model procedure calls, but can’t validate SOAP body with an XML Schema
Entire body complies with an XML Schema
containing element doSomething containing
a sequence of elements foo and bar
Wrapped style. Notice the operation
has one message part called “parameters”
which is an XML sequence of the args
Write code first and use doc/literal style. i.e. Every method has one arg. Use
annotations to name everything and review
Will other projects be using these services? i.e. is this part of an SOA?
Are you in a great hurry?
Write code first in
wrapped/literal style, i.e. Use
annotations to name everything and review WSDL afterward.
Write WSDL first.
Think through interfaces carefully, plan
for backward compatibility, write lots of
comments, and maintain in source control.