Future WCF developers will frequently define service and message contracts, but using mes-
sage contracts to explicitly define the message structure will likely be less common. This can
prove useful if you need to interoperate with another (non-WCF) service, which requires a
particular message format.
To define a message contract, you use the MessageContract, MessageHeader, and
MessageBody attributes as shown here:
Future WCF developers will frequently define service and message contracts, but using mes-
sage contracts to explicitly define the message structure will likely be less common. This can
prove useful if you need to interoperate with another (non-WCF) service, which requires a
particular message format.
To define a message contract, you use the MessageContract, MessageHeader, and
MessageBody attributes as shown here:
sage contracts to explicitly define the message structure will likely be less common. This can
prove useful if you need to interoperate with another (non-WCF) service, which requires a
particular message format.
To define a message contract, you use the MessageContract, MessageHeader, and
MessageBody attributes as shown here:
0 comments:
Post a Comment