I am brand new to WCF, and have limited experience coding against web services.
At work it has been dictated to use WCF for everything network service oriented. The work I need to do involves querying a non-WCF web service, apparently built in Java, with a Netscape certificate server and related infrastructure (the service is not under our control). I have the WSDL for the web service.
-
Does WCF add any value to this job?
-
Is it reasonable, normal, or a best practice to build a WCF client against a non-WCF service?
-
Can anyone offer any advice in doing this?
Thanks!!!
Yes, a WCF client can work against a web service created with another technology or platform. It’s fairly common. With Visual Studio, the client side proxy code is generated for you from the WSDL, and you can invoke a remote service as if it was a local code.
Not to pull a shameless plug, here’s a sample of a WCF client calling the Amazon S3 web service, which is quite certainly not built with .NET. The sample demonstrates a typical workflow when creating a WCF client:
Add a Service Reference to the web service, by pointing Visual Studio at the WSDL URL. You don’t have to code anything in this step.
Invoke the web service from your code. In the code below, the AmazonS3Client class was created by Visual Studio in step 1 above. You get full intellisense when typing client.ListAllMyBuckets to invke that service.