Note: If the above links do not take you to the referenced specification, the OMG may have changed the URL. You can search the Object Management Group website for the correct specification.
Supported Specification Details
Not all of the above specifications are implemented in the WebLogic ORB in this release. The following section provides a precise list of the supported specifications by chapter or section:
CORBA 2.3.1, chapters 1-7.
CORBA 2.3.1, sections 10.6.1 and 10.6.2 are supported for repository IDs.
CORBA 2.3.1, section 10.7 for TypeCode APIs.
CORBA 2.3.1, chapters 13 and 15 that define GIOP 1.0, 1.1, and 1.2. The WebLogic Server 8.1 ORB supports all versions of GIOP including the bi-directional GIOP feature defined in sections 15.8 and 15.9.
The Interoperable Naming Service.
Section 1.21.8 of the Revised IDL to Java Language Mapping Specification (ptc/00-11-03) has been changed from the version in the IDL to Java Language Mapping Specification (ptc/00-01-08).
Transaction Service 1.2.1, as defined by the EJB 2.0 specification.
CORBA 2.6, chapter 26, conformance level 0 plus stateful.
For this release, the WebLogic ORB is compliant with the following tools:
The IDL to Java compiler (idlj) is compliant with following specification references:
CORBA 2.3.1, chapter 3 (IDL definition).
CORBA 2.3.1, chapters 5 and 6 (semantics of Value types).
CORBA 2.3.1, section 10.6.5 (pragmas).
The IDL to Java mapping specification.
The Revised IDL to Java language mapping specification section 1.12.1 (local interfaces).
The Java to IDL compiler (the IIOP backend for rmic) complies with:
CORBA 2.3.1, chapters 5 and 6 (value types).
The Java to IDL language mapping. Note that this implicitly references section 1.21 of the IDL to Java language mapping.
IDL generated by the -idl flag complies with CORBA 2.3.1, chapter 3.
Other Compatibility Information
The java.util.Calendar class is not interoperable between J2SE 1.3.x and WebLogic Server 8.1 when using RMI-IIOP. OMG issue 3151 may provide a solution for this issue but it is more likely that the solution will be implemented in a later release of the Java platform.
The J2SE v.1.4 version of the java.util.Calendar class writes a ZoneInfo object in its writeObject method and calls a readObject to read the object. When the J2SE 1.4 java.util.Calendar class is serialized, it expects that if it is talking to an older J2SE version, the ZoneInfo object should not be present. In this situation, the stream will throw an EOFException exception and keep the stream position intact.