I have been using WSE 3.0 for a while now and I really like it.
I really like the policy mechanism in the WSE, it affords me a kind of AOP (aspect orientated programming) that I am really starting to get into.
For instance I have made a lot of SoapFilters recently, some handy, some just for tests, but each of them allow me to add an aspect of functionality into the webservice that I am creating in a configuration and not a design time.
If I want security, just add a policy line in the XML config, if I want auditing another line, if I want exception shielding another line.
All of these aspects of the system I am creating can be added at deployment time thus leaving my web service code clean and simple.
An example, pseudo code:
And a policy file (not an actual file that would work in this example) would say:
This service code and policy file model is so much cleaner and simpler than what you would have to write if you didn’t have an AOP style policy system:
Now tell me which code you would like to maintain! 🙂
Tags: asp.net, WSE, WSE3, c#, .net, webservice
Technorati:
Add to 
Bookmark Murdok:
Paul Kinlan is the author of the popular C#, .Net Framework blog. Paul is an Analyst Developer working in Southport, England. Paul has several years experience developing and designing massively scalable enterprise systems on UNIX and Windows based architectures.
