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/ and vice versa.
Interoperability tests were completed on JAX-RPC Web Services in the following areas:
In addition, the following combined features were tested:
The following sections describe the interoperability issues and guidelines that were identified during the testing.
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
The following lists interoperability guidelines for WS-Security:
<sp:Strict>layout assertions (shown below) cannot be guaranteed.
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.
The following lists interoperability guidelines for WS-SecureConversation:
<sp:EndorsingSupportingTokens>) is not supported.
<sp:EncryptBeforeSigning/>unless there is a security requirement. Instead, use
<sp:BootstrapPolicy>policy assertion, you should refer to the guidelines defined in WS-Security Interoperability Guidelines.
Compatibilityflag must be set on the server side via the Web service Security MBean using the
Compatibilityflag set, the client must set this flag as well, as follows:
The following lists interoperability guidelines for WS-ReliableMessaging:
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 thesite: