How to avoid coupling using custom type in web service

Question

I'm going to develop a webservice (likely in WCF) and probably several parameters passed to the exposed methods will be custom type parameters.

Do you have any hints on how to avoid breaking SOA decoupling and reach my target?

Thanks!

Answer 1

WSDL defines interoperable contract with :

• endpoint and action describing how to communicate with webservice
• types using and xsd schema

The xml schema (xsd) describes types : xml elements, value types using xml types and so on.

So if you can describe all your types using Xml Schema, then it will be ok. .NET enforce your type can be serialized to xml, then it is possible to expose it via a webservice.

On the client side, there are often libraries which can read WSDL and deduct/generate classes in their language to serialize/deserialize messages to/from the service. But any human can also read the contract and the writ