Geek asks and answers

How to make a decision between the Transfer Agreement and the Data Agreement in WCF?

I read so many things to understand different things in WCF.

Very soon, in fact, I want to move / convert existing WSE3 web services to WCF. In existing WSE web services, I have some (data) classes that model objects in our environment.

When converting these classes, you should use the Data Contract / Data Member attribute or the MessageContract attribute?

1. How to make a decision between the Transfer Agreement and the Data Agreement in WCF? 2. Does the type of binding (for example, basicHttpBinding) have any role in this solution? 3. Are proxies created on the client side (when adding a web link) are created, significantly depending on the data contract or message?

(PS: I'm trying to find a way that existing WSE clients should be able to consume the WCF service without any major changes / modifications. Is it possible to use current proxies created from ASMX web services to connect to the new WCF service by simply setting the proxy URL servers for the WCF service?)

+3
source share
2 answers

Here is a quick answer to your questions:

1) If there is no specific reason, for example, to customize the structure of soap XML, use a DataContract instead of a MessageContract.

2 and PS) Since you use soap through HTTP, you will most likely need new services that will be configured for basicHttpBinding. This will provide the interoperability you need for ASMX customers.

3) , , WCF, .

, WSE 3.0 WS- *. , wsHttpBinding , , ASMX wsHttpBinding.

+3

, SOAP. DataContract , , . MessageContract - , , SOAP.

WCF SOAP, WSE3. , ? ( ) Xml, WCF, XML.

Btw. WSE3 ASMX? ? . BasicHttpBinding .

- , , . .

+2

More articles:


All Articles