IBM User Guide for Java V7 on Windows > Developing Java applications
CORBA support
The Java™ Platform, Standard Edition (JSE) supports, at a minimum, the specifications that are defined in the compliance document from Oracle. In some cases, the IBM JSE ORB supports more recent versions of the specifications.
The minimum specifications supported are defined
in the Official Specifications for CORBA support in Java SE 7: 
http://download.oracle.com/javase/7/docs/api/org/omg/CORBA/doc-files/compliance.html.
Support for GIOP 1.2
This SDK supports all versions of GIOP, as defined by chapters 13 and 15 of the CORBA 2.3.1 specification, OMG document formal/99-10-07. http://www.omg.org/cgi-bin/doc?formal/99-10-07
Bidirectional GIOP is not supported.
Support for Portable Interceptors
This SDK supports Portable Interceptors, as defined by the OMG in the document ptc/01–03–04, which you can obtain from:
http://www.omg.org/cgi-bin/doc?ptc/01–03-04
Portable Interceptors are hooks into the ORB that ORB services can use to intercept the normal flow of execution of the ORB.
Support for Interoperable Naming Service
This SDK supports the Interoperable Naming Service, as defined by the OMG in the document ptc/00-08-07, which you can obtain from:
http://www.omg.org/cgi-bin/doc?ptc/00-08-07
The default port that is used by the Transient Name Server (the tnameserv command), when no ORBInitialPort parameter is given, has changed from 900 to 2809, which is the port number that is registered with the IANA (Internet Assigned Number Authority) for a CORBA Naming Service. Programs that depend on this default might have to be updated to work with this version.
The initial context that is returned from the Transient Name Server is now an org.omg.CosNaming.NamingContextExt. Existing programs that narrow the reference to a context org.omg.CosNaming.NamingContext still work, and do not need to be recompiled.
The ORB supports the -ORBInitRef and -ORBDefaultInitRef parameters that are defined by the Interoperable Naming Service specification, and the ORB::string_to_object operation now supports the ObjectURL string formats (corbaloc: and corbaname:) that are defined by the Interoperable Naming Service specification.
The OMG specifies a method ORB::register_initial_reference to register a service with the Interoperable Naming Service. However, this method is not available in the Oracle Java Core API at this release. Programs that have to register a service in the current version must invoke this method on the IBM internal ORB implementation class. For example, to register a service "MyService":
((com.ibm.CORBA.iiop.ORB)orb).register_initial_reference("MyService",
serviceRef);
Where orb is an instance of org.omg.CORBA.ORB, which is returned from ORB.init(), and serviceRef is a CORBA Object, which is connected to the ORB. This mechanism is an interim one, and is not compatible with future versions or portable to non-IBM ORBs.
- System properties for tracing the ORB
A runtime debug feature provides improved serviceability. You might find it useful for problem diagnosis or it might be requested by IBM service personnel. - System properties for tuning the ORB
The ORB can be tuned to work well with your specific network. The properties required to tune the ORB are described here. - Java security permissions for the ORB
When running with a Java SecurityManager, invocation of some methods in the CORBA API classes might cause permission checks to be made, which might result in a SecurityException. If your program uses any of these methods, ensure that it is granted the necessary permissions. - ORB implementation classes
A list of the ORB implementation classes.
Parent: Developing Java applications
Error 404 - Not Found
The document you are looking for may have been removed or re-named. Please contact the web site owner for further assistance.