This is great start tyvm!!What language? Java use GSON for JSON: https://github.com/google/gson
REST: http://www.vogella.com/tutorials/REST/article.html or https://spring.io/guides/gs/rest-service/
Wow well let me put together a small description of I suppose would be an average Soap request/post. Some kind of starting point I can wrap my head around. Thanks for your help![MENTION=222878]Solarion[/MENTION]
Im a webservices expert specialising in SOAP services and C# front ends.....
Where exactly are you stuck?I write client side, server side and everything inbetween
Did you check my library?Well, several months later and still have only ever been able to log into a web service. That's about it. The entire concept of SOAP just completely baffles me.
I have all the information I need but just cannot come right with this. Feel kind of cursed when it comes to web services.
I might actually make a giant poster that reads: "The remote server returned an error: (400) Bad Request." and hang it in my room as a eulogy to my ordeal.
Think of it as a company's web service stuck in the early 2000's that like spending excessive bandwidth and man-hours with convoluted XML messages.The entire concept of SOAP just completely baffles me.
Thanks Thor I'm not ignoring you I will check it out thanks buddy, however I think I may need to go back to basics, rewind a bit and figure out what I missed. Something vital.Did you check my library?
I understand that you need a header and a XML string, serialized from a class. I was able to achieve this with a Order > Line Items type class; to serialize it into XML.Think of it as a company's web service stuck in the early 2000's that like spending excessive bandwidth and man-hours with convoluted XML messages.
Anyway, there's not much to it...it's a piece of XML in a specific format sent to a server. It's got a HEADER section with all sorts of metadata in it and a BODY section where you dump your XML into (usually they'll give you an XSD to work with).
You send them a SOAP message and they send you a response. If it is async you'll find some sort of correlation ID in the HEADER to match it with whatever you sent earlier.
Enterprises that spent too much money on Websphere MQ love SOAP messages because that's what their manual says is the gold standard in building distributed systems that scale to levels only ever witnessed before in Ancient Rome. Or the architect is kanniedood 70 year old from the COBOL days.
If you are using C# via Visual Studio you can point it to the webservice and it will magically generate all the classes for you.
TL;DR: SOAP is a simple JSON message's fat cousin with diabetes one broker away from having a stroke.