Sending data to a webservice

Johnatan56 said:
What language? Java use GSON for JSON: https://github.com/google/gson
Tutorial: https://futurestud.io/tutorials/gson-getting-started-with-java-json-serialization-deserialization
REST: http://www.vogella.com/tutorials/REST/article.html or https://spring.io/guides/gs/rest-service/

C#: https://www.newtonsoft.com/json
Tutorials: https://www.newtonsoft.com/json/help/html/SerializingJSON.htm
Click to expand...

This is great start tyvm!!

I'm going to look at getting some kind of WPF/mvvm training course done. Thanks for the helpful info guys much appreciated.
 
[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 :D
 
Last edited:
Solarion said:
This is great start tyvm!!

I'm going to look at getting some kind of WPF/mvvm training course done. Thanks for the helpful info guys much appreciated.
Click to expand...

For what you require this isnt necessary as that simple form wont need MVVM.
 
Batista said:
[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 :D
Click to expand...

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!
 
Last edited:
From Visual Studio, it's very easy to interface with SOAP web services. All you need to do is right-click and references and select "Add Service Reference" and then enter the URL for the SOAP service WSDL.
It will then automatically generate all your proxy classes for working with the service and setup the standard config.

You then need to create a new instance of the client / proxy class, Open a connection to the service and then execute any command.
 
I'll upload my nusoap library with some examples to github sometime this weekend, might help you.
 
Dude I could have helped you do your thing in an hour.Next time you get another request like that just hit me up.
 
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.
 
Solarion said:
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.
Click to expand...
Did you check my library?
 
Solarion said:
The entire concept of SOAP just completely baffles me.
Click to expand...
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.
 
Last edited:
Thor said:
Did you check my library?
Click to expand...

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.

Hamster said:
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.
Click to expand...

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.

I seem to hit a brick wall at the Action to send to the server (Insert, Update, Delete). Somewhere between CRUD and Post etc it all falls apart.

Someone on the forum is helping me at the moment with wrapping my head around it.

Web services are so important and it's a vital too to have in your toolbox. I'm kind of OCD about learning it now because it's been bugging me a while, possibly about 5 years now.

I've put everything else on hold at the moment until I crack this.
 
Download SoapUI
Load the WSDL into SoapUI
It will generate the requests
Run a request
View the raw tab, it will show you exactly what was sent, including the action.
SoapAction is just an HTTP header name/value
 
@Solarion
As much hate as the guys here has for SOAP it's still the most prevalent form of communication we use.
I have written a huge number of webservices and consume just as many from other companies, so it's second nature at this stage.

What language are you running on the server hosting the webservice?
What language is your website in?
Is the webservice already written or do you have to write it?
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X