JAV2I13 — Issue with ValueHandler.getRunTimeCodeBase and PRO.exportObject

1. The Java to IDL mapping spec defines the ValueHandler.getRunTimeCodeBase() that returns an CORBA object reference of SendingContext::RunTime to be used to construct the SendingContextRunTime service context:

org.omg.SendingContext.RunTime getRunTimeCodeBase();

However, the ValueHandler is not ORB aware of, how should the object reference be constructed by the ValueHandler? More specifically, how should the ValueHandler get a handle of a POA and which POA to create the reference?

2. Similar issue exists in PortableRemoteObject.exportObject() and PRO constructor:

protected PortableRemoteObject() throws java.rmi.RemoteException;
public static void exportObject(java.rmi.Remote obj) throws java.rmi.RemoteException;

The spec says:

"Server side implementation objects may either inherit from javax.rmi.PortableRemoteObject or they may simply implement an RMI/IDL remote interface and then use the exportObject method to register themselves as a server object"

The PRO is again not ORB aware of, how should the remote object be exported and registered with a POA and with which POA?

3. The spec needs to clearly indicate on who owns the creation/initialization of the ORB. Should rmi-iiop implementation implicitly create/initialize an ORB instance at some point of time? Or should the RMI-IIOP application create/initialize an ORB instance and pass into the RMI-IIOP implementation via certain APIs?

Closed, accepted. See revised text below