Question

I have to define a web service contract that afterwards will be used by different software suppliers to implement their servers and clients.

I tried to do it defining classes, making a WCF service and using it to autogenerate WSDL document. The problem with this approach is that inside WSDL there are some specifics concerning binding and the web service address.

How to achieve generating a web service contract without such implementation specific information?

Thank you in advance.

Best regards,
Łukasz Głaz

Was it helpful?

Solution 2

I have found out that using namespaces appropriately it is possible to autogenerate abstract parts of the server definition into one WSDL file and one XSD file and the implementation specific parts (binding and service elements) into another WSDL file. In this way I get the separation I wanted.

OTHER TIPS

In my opinion, the absolute best way to do this would be to not generate the WSDL at all - create it by hand. Generate your various contract classes from the WSDL, and use those to implement the service.

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top