We’ll go step by step.
- What are WS* Specifications
- What are WSE Enhancements
- There are a variety of specifications associated with web services. These Web service specifications are occasionally referred to collectively as "WS-*". The reference term "WS-*" is more of a general nod to the fact that many specifications are named with "WS" as their prefix
- These specifications are in varying degrees of maturity and are maintained or supported by various standards bodies and entities.
- Specifications may complement, overlap, and compete with each other.
The specifications lie under different heads.
- Web Service Standards Listings
- XML Specifications
- Messaging Specifications
- Metadata Exchange Specifications
- Security Specifications
- Reliable Messaging Specifications
- Resource Specifications
- Web Services Interoperability organization (WS-I) Specifications
- Business Process Specifications
- Transaction Specifications
- Management Specifications
- Presentation Orientated Specification
- Draft Specifications
Here are the details on each.
Web Service Standards Listings
These sites contain documents and links about the different Web Services standards identified on this page.
* IBM's Web Services Standards Page
* Microsoft's Web Services Standards Page
* World Wide Web Consortium's Web Services Activity
* innoQ's WS-Standards Poster
* OASIS Standards and Other Approved Work
* XML CoverPages
* Open Grid Forum Final Documents
* XML (eXtensible Markup Language)
* XML Namespaces
* XML Schema
* XML Information Set
* XML Pointer
* SOAP (formerly known as Simple Object Access Protocol)
* SOAP Message Transmission Optimization Mechanism
Metadata Exchange Specifications
* Universal Description, Discovery, and Integration (UDDI)
* WSDL 2.0 Core
* WSDL 2.0 SOAP Binding
o Web Services Semantics (WSDL-S)
* WS-Resource Framework (WSRF)
* XML Signature
* XML Encryption
* XML Key Management (XKMS)
* WS-Federation Active Requestor Profile
* WS-Federation Passive Requestor Profile
* Web Services Security Kerberos Binding
* Web Single Sign-On Interoperability Profile
* Web Single Sign-On Metadata Exchange Protocol
* Security Assertion Markup Language (SAML)
Reliable Messaging Specifications
* WS-RM Policy Assertion
* Web Services Resource Framework
* Resource Representation SOAP Header Block
Web Services Interoperability organization (WS-I) Specifications
These specifications provide additional information to improve interoperability between vendor implementations.
* WS-I Basic Profile
* WS-I Basic Security Profile
* Simple Soap Binding Profile
Business Process Specifications
* Web Services Choreography Interface
* XML Process Definition Language
* WS-Management Catalog
Presentation Orientated Specification
Web Services for Remote Portlets
WS-Provisioning Describes the APIs and Schemas necessary to facilitate interoperability between provisioning systems in a consistent manner using Web services
- WSE is an add-on to the Web Services, and enables to implement the above mentioned WS-* Web service specifications - but chiefly in areas such as Security, Reliable Messaging, and Sending Attachments.
- WSE provides extensions to the SOAP protocol i.e. SOAP protocol extensions and allows the definition of custom security, reliable messaging, policy, etc.
- Developers can add these capabilities at design time using code or at deployment time through the use of a policy file.
There are multiple versions of WSE.
- For .NET Framework 1.0 was released in December 2002.
- It was based on the draft version of WS-Security.
- It is not supported anymore and is not compatible with .NET 2.0.
- It uses the older "XMLSOAP" namespace in contrast to the OASIS namespace used by WSS4J and WSE 2.0/3.0.
- Released for Visual Studio .NET 2003 and the .NET Framework 1.1 in May 2004.
- It introduced major secure communication improvements (signing and encryption of user-defined SOAP headers, Kerberos Security Context Tokens, delegated trust etc), a new lightweight messaging infrastructure, a new programming model, support for SOAP based messaging over TCP as an alternative to HTTP, a policy framework based on WS-Policy and WSDL, WS-Addressing, WS-Trust, WS-SecureConversation support.
- WSE 2.0 can be used from within standalone executables and Windows services i.e. outside IIS in addition to ASP.NET applications.
- It is also compatibile with .NET 2.0, however it does not have design time support with Visual Studio 2005.
- It is not interoperable with WSE 3.0 and WCF.
· Released in October 2005 and has design time support with Visual Studio 2005.
· It includes policy framework enhancements including security based on policy assertions (associating CLR client proxies with policy files), turnkey security scenarios for securing end to end messages, extensibility mechanisms for user-defined policies in code and a simplified policy model applied to a message exchange instead of on a per-message level.
· It supports updated Web services specifications and a native 64-bit runtime. WS-SecureConversation sessions can be cancelled explicitly and sessions are reliable and usable in web farm scenarios as Security Context Tokens can contain the original client authentication token when sent from the client to the service, which enable sessions to be re-established if lost, e.g. when a service's appdomain is reset.
· WSE 3.0 is wire-level interoperable over HTTP with WCF and supports the same version of the WS-* specifications as WCF (WS-Security 1.1, SOAP 1.2, MTOM).
Note: It seems that there is no WSE 4.0 to work with VS2008. Instead, VS 2008 relies on WCF for the same functionality.
Hope this helps.