Introducing WebLogic Web Services

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Interoperability with Microsoft WCF/.NET

In conjunction with Microsoft, Oracle has performed interoperability testing to ensure that the Web Services created using WebLogic Server can access and consume Web Services created using Microsoft Windows Communication Foundation (WCF)/ .NET 3.0 and 3.5 Framework and vice versa.

Interoperability tests were completed on JAX-RPC Web Services in the following areas:

Table 4-1 Completed Interoperability Tests 
Interoperability Guidelines
Basic and complex data types
Web Services Security (WS-Security) 1.0 and 1.1
Web Services Security Policy (WS-SecurityPolicy) 1.2
Web Services Secure Conversation Language (WS-SecureConversation) 1.3
Web Services Policy Framework (WS-Policy) 1.5
No interoperability guidelines provided.
Web Services Addressing (WS-Addressing) 0.9 and 1.0
Message Transmission Optimization Mechanism (MTOM)
Web Services Reliable Messaging (WS-ReliableMessaging) 1.0 and 1.1
Web Services Trust (WS-Trust) 1.3

In addition, the following combined features were tested:

The following sections describe the interoperability issues and guidelines that were identified during the testing.

Basic Data Types Interoperability Guidelines

When using the anyType class with Microsoft .NET 3.0/3.5 the Java data type returned cannot be guaranteed. If a specific Java data type is required, avoid using anyType.

WS-Security Interoperability Guidelines

The following lists interoperability guidelines for WS-Security:

WS-SecurityPolicy Interoperability Guidelines

In this release, WebLogic Server supports Web Services Security Policy (WS-SecurityPolicy) 1.2. Microsoft .NET 3.0 supports the December 2005 draft version of the WS-SecurityPolicy specification.

In the December 2005 draft version of the specification, the <sp:SignedEncryptedSupportingTokens> policy assertion is not supported. As a result, Microsoft .NET 3.0 encrypts the UsernameToken in the <sp:SignedSupportingTokens> policy assertion. If you use the <sp:SignedSupportingTokens> policy assertion without encrypting the UsernameToken, the WebLogic Server and .NET Web Services will not interoperate.

WS-SecureConversation Interoperability Guidelines

The following lists interoperability guidelines for WS-SecureConversation:

WS-ReliableMessaging Interoperability Guidelines

The following lists interoperability guidelines for WS-ReliableMessaging:

WS-Trust Interoperability Guidelines

WebLogic Server does not interoperate with Microsoft .NET according to the .NET interoperability scenarios that use both SAML and WS-Trust, as defined in the following documents on the Microsoft .NET Web Services Interoperability site:

  Back to Top       Previous  Next