There is nothing to fear, add a wsdl and if that was not enough, also add web api.
The exposing of services is the easiest part, the hard part is already implemented. How many services are we talking about here? On Fri, 10 Jul 2015 at 7:00 pm Greg Keogh <[email protected]> wrote: > Folks, we have a WCF basic http binding service that has been in > production use for many years, but so far the only clients have been .NET > desktop and Sliverlight apps. They can of course use a proxy class > generated by svcutil.exe and it's all easy peasy. > > Now the time has come to open the service up to other clients such as apps > on phones and tablets written in Objective-C, Swift, Java and perhaps > JavaScript. We haven't had any of these clients consume our service yet, > but it may only be weeks away. A Java guy told me that if he has the WSDL > then it won't be a problem, but I fear there may be devils in the details. > I quite worry that the svcutil generated code contains stubs of all C# > classes that are public in the service and can't imagine how they would > transformed for consumption by different clients. > > I fear that our SOAP style service is too specific and old fashioned to be > easily consumed by non .NET clients. I'd be interested to hear if anyone > can confirm this or has general comments in this area. I'm guessing a REST > style would be best for everyone, but what will it return, XML, JSON, or > both? > > *Greg K* >
