Writing a SOAP client over SSL
Hi All,
I want to write in C#, a SOAP client over an SSL connection to a server which supports SOAP requests and gives back SOAP responses.
The way i am currently doing it is
1) I use a open source .NET SSL library to connect to the server.
2) I manually create SOAP requests(in the form of strings stored as resource and in XML files) and send these request over the connection created in 1.
3) I get back the response over the SSL connection and then parse it to get the response.
Now my question is, Can i a use .NET framework class library which provides all these features, so that i can just create a SOAP web service client(which would work over SSL) and then use these .NET web service classes to actually get my work done.
Any help or direction would be really appreciated.
Thanks
Vinu
[822 byte] By [
thambi] at [2008-2-20]
I know this is an old posting but I have ran into the same issue and was doing a search for similar issues.
In C# changing the http to https works fine. In my VC++ project it does not work when I change the http to https. I get a SOAP_SEND_ERROR. I can't figure out why there's no problem in C# but VC++ gives me problems. There is no problems updating the web reference or compiling but I get a SOAPCLIENT_SEND_ERROR.
I created both project in VS 2003. I just installed VS 2005, converted the project to 2005, and WSE 3.0 thinking this might fix the problem but it doesn't.
Any help would be appreciated.
Brother C
I agree, the wsdl parser makes creating proxy classes for asp.net webservices a brainless activitiy :-)
However, recently I worked on a project to access a Axis/Apache build webservices where half of the SOAP methods couldn't be called effectively although the proxy classes where created. I had to turn to the MSXML2 COMponent to get a valid soap response to my soap request. SOAP apperently is great if you use SAX in a java/Apache/Axis environment and the .NET Webservices classes are just great to build webservices and clients in .NET. But don't expect any operability to work on a mixed environment when deadlines are tight. What MS (or the open/source Apache/Axis community for that matter) failed to realize is that SOAP 's intention where primarily interoperabilty, and with interoperability I mean talking to a LAMP environment to a MS one and vice versa. If there is someone with that experience I'd be offering him/her a job on the spot :-)
 Daniel Roth wrote: |
| You can very easily use a web service client proxy to send SOAP messages to a server over SSL. Simply generate a web service client proxy using a URL that starts with https instead of http. The https protocol is just HTTP over SSL. Daniel Roth |
|
