It is clear that in order to be able to call your service, you need to mark the contract interface/class with the ServiceContractAttribute. After this post, it’ll be also clear that you must mark your exposed methods with the OperationContractAttribute. In most cases you’ll be satisfied with the default settings, but there are certain cases (one-way or duplex messaging pattern) when you need to customize the OperationContractAttribute.
Fortunately, it exposes a set of named parameters for implementing such behaviors. Here’s a brief list of them:
|Named Parameters of OperationContractAttribute|
|Action||Controls the action on the request message. The default value is the fully qualified name of the method as an address, for example: http://TheServices/IContract/MyMethod. Set it to an asterisk to indicate an operation which handles all unmatched requests. There’s a constraint on this: there can be only one method like this, and it must take a message as parameter.|
|AsyncPattern||A Boolean value indicating whether the current pattern is asynchronous.|
|IsInitiating||A Boolean value indicating the marked method is the initiation of a session. The default is true.|
|IsOneWay||A Boolean value indicating that the operation returns nothing, and has no output parameters. The default is false. When you set this to true, and return anything else than void, an InvalidOperationException will be thrown at run time.|
|IsTerminating||A Boolean value indicating that after this method the session should be terminated, and the channel closed.|
|Name||Overrides the operation name from the default value: the contract’s method name. This is interesting from the clients point of view. They can call your through the proxy class by the name you specify here (think about IntelliSense support).|
|ProtectionLevel||A member of the System.Net.Security.ProtectionLevel enumeration, indicating the level of protection required by the method.|
|ReplyAction||Controls the action on the reply message. Use it in conjuction|
If you could recall the previous post about Service contracts, I mentioned that you must use serializable types as return/parameter types in your exposed methods. When you build custom types (and you’ll certainly do so) you’ll need to tell WCF either implicitly or explicitly how to serialize your types.
The implicit way is to mark your custom types as serializable, with the SerializableAttribute class. This isn’t too exciting, and doesn’t require you to use data contracts, which are cooler, and will be covered by the exam test. Anyway, you should know that all publicly visible properties and fields will be serialized when you use the implicit method.
The explicit way is to mark your custom types with the DataContractAttribute and the fields/properties with the DataMemberAttribute. Then you’ll gain a finer control over how WCF will serialize and deserialize those types. The DataContractAttribute has the following named parameters:
A service contract is used to define the set of operations a service exposes, its signature, the data types used, the location of the operations and the specific protocols and serialization format of the service.
In WCF, the best practice is to define the service contract as a .NET interface, and implement that interface by your service class. If you expose only some static and not-too-often changing methods in your service, you can omit the interface, and define the contract in the class.
To define the WCF service contract, you’d typically mark your contract interface with the ServiceContractAttribute, but more on this a little bit later.
At the end of the day, XML service contracts will be generated based on your interfaces and contracts, which can be exposed (and understood) by other applications, even those running on different platforms. This is the real power of services, in one word: interoperability.
Now enough of such high level abstraction, let’s dig ourselves into the layer where the actual work is done, and see how to design and implement our service contracts. First the design:
In SOA (Service Oriented Architecture) a service is a self-explaining unit of functionality. Viewed from this aspect, a class or interface is nothing more than a group of related methods and functions, exposed to the client.
Generally, it’s a better idea to use .NET interfaces as service contracts, because:
- Service contract interfaces can extend any number of other contract interfaces
- A class can implement any number of interfaces, thereby any number of contracts
- You can easily modify the service implementation in the class, while the service contracts encapsulated in an interface remains the same
- Versioning is enabled by implementing the old interface in a new one
As I promised, the learning continues. My next goal is the Windows Communication Foundation exam, with the number of 70-503. I’ll use the book Pro WCF by Chris Peiris and Dennis Mulder as my primary learning resource, and MSDN. I won’t buy the Training Kit, because of the lack of time (books ordered from Amazon arrive to Hungary in more than a week, and time is short till 30th).
I think this time I won’t use MeasureUp to practice, maybe I know enough of the format of exam questions by now (or maybe I don’t). Anyway, expect 30 posts about this one, I want to go through the syllabus in much more detail than in the previous times.