UPDATE: I added ASMX 1.x to the table.
As I am currently investigating into some interoperability scenarios
between the .NET and Java worlds I thought you may be interested in a
list of supported WS-* specifications for .NET today and tomorrow.
Only out-of-the-box features and support is mentioned. I hope that there are no mistakes in this table...
|
Category |
Protocol / Technology |
ASMX 1.x |
ASMX 2.0 |
WSE 2.0 |
WSE 3.0 |
WCF |
|---|---|---|---|---|---|---|
| Core | Basic Profile 1.1 | X** | X | X | X | X |
|
|
SOAP 1.1 | X | X | X | X | X |
|
|
SOAP 1.2 | - | X | - | X | X |
| WS-Addressing | - | - | X | X | X | |
| Opaque Data Transfer | DIME | - | - | X | - | - |
| MTOM | - | - | - | X | X | |
| Other Transports & Encodings | TCP | - | - | X | X | X |
|
|
UDP | - | - | - | - | - |
|
|
HTTP | X | X | X | X | X |
| MSMQ | - | - | - | - | X | |
| Named Pipes | - | - | - | - | X | |
|
|
Text-XML | X | X | X | X | X |
|
|
Binary-Encoded XML | - | - | - | - | X |
| Binary Serialization | - | - | X* | X* | - | |
| Security | WS-Security 1.0 | - | - | X | X | X |
|
|
WS-Security 1.1 | - | - | - | X | X |
|
|
WS-SecureConversation | - | - | X | X | X |
|
|
WS-Trust | - | - | X | X | X |
|
|
Basic Security Profile 1.0 | - | - | X | X | X |
| SAML 1.1 | - | - | - | - | X | |
| Reliability | WS-ReliableMessaging | - | - | - | - | X |
| Transactions | WS-Coordination | - | - | - | - | X |
| WS-AtomicTransaction | - | - | - | - | X | |
| Metadata, Policy & Binding | WS-MetadataExchange | - | - | - | - | X |
|
|
WSDL 1.1 | X | X | X | X | X |
|
|
WS-Policy | - | - | - | - | X |
|
|
WS-PolicyAttachment | - | - | - | - | X |
|
|
WS-SecurityPolicy | - | - | - | - | X |
| WS-ReliabilityPolicy | - | - | - | - | X |
* custom WSE-specific serialization, not compatible with WCF
** need to be aware what feature to use; no proactive checks for conformance
WSE 2.0 support WS-Policy.
Posted by: Diego Gonzalez | 10/21/2005 at 09:49 PM
What about WS-Eventing?
Posted by: Shahrokh Shirzad | 10/22/2005 at 10:29 AM
Any spec that is not listed is not supported by any technology stack in their mentioned version out-of-the-box. Thanks.
Posted by: Christian Weyer | 10/22/2005 at 11:41 AM
Support for WS-Policy, WS-SecurityPolicy, and WS-PolicyAssertions has been available since WSE 2.
Posted by: SDV | 10/26/2005 at 08:54 PM
Support for WS-Policy, WS-SecurityPolicy, and WS-PolicyAssertions has been available since WSE 2.
Posted by: SDV | 10/26/2005 at 08:55 PM
SDV; when speaking about real protocol support, WSE does not support any of the above mentioned (WS-Policy, WS-SecurityPolicy, and WS-PolicyAssertions)... they use it internally, yes, maybe. But this does not matter at all to the rest of the world. WSE does not 'emit' any metadata for consuming services based on those specs. If this is wrong, please let me know...
Posted by: Christian Weyer | 10/27/2005 at 04:53 PM
Hi Christian, The WSE team has made a WS-ReliableMessaging implementation for WSE 3.0
Posted by: Pablo Cibraro | 11/04/2005 at 09:54 PM
One minor point about TCP support -- the framing format used to bind Messages to TCP is different between WSE 2.0, WSE 3.0, and WCF. So while they all have TCP as a transport, they do not interop with each other.
Posted by: Kenny Wolf | 11/09/2005 at 12:57 AM
It would be easier to read if the ASMX 2.0 and WSE 2.0 columns are exchanged (a time scale axis, sort of).
Posted by: Giulio Vian | 12/14/2005 at 01:37 PM