Stubs and ties generation
The RMI-IIOP code provides the tools to generate stubs and ties for whatever implementation exists of the client and server.
The following table shows what command to run to get the stubs
and ties (or skeletons) for each of the three techniques:
| CORBA | RMI(JRMP) | RMI-IIOP |
|---|---|---|
idlj Sample.idl |
rmic SampleImpl |
rmic -iiop Sample |
Compilation generates the files that are shown in the following
table. To keep the intermediate .java files,
run the rmic command with the -keep option.
| CORBA | RMI(JRMP) | RMI-IIOP |
|---|---|---|
| Sample.java | SampleImpl_Skel.class | _SampleImpl_Tie.class |
| SampleHolder.java | SampleImpl_Stub.class | _Sample_Stub.class |
| SampleHelper.java | Sample.class (Sample.java present) | Sample.class (Sample.java present) |
| SampleOperations.java | SampleImpl.class (only compiled) | SampleImpl.class (only compiled) |
| _SampleStub.java | ||
| SamplePOA.java (-fserver, -fall, -fserverTie, -fallTie) | ||
| SamplePOATie.java (-fserverTie, -fallTie) | ||
| _SampleImplBase.java (-oldImplBase) |
Since the Java™ v1.4 ORB, the default object adapter (see the OMG CORBA specification v.2.3) is the Portable Object Adapter (POA). Therefore, the default skeletons and ties that the IDL compiler generates can be used by a server that is using the POA model and interfaces. By using the idlj -oldImplBase option, you can generate older versions of the server-side skeletons that are compatible with servers that are written in Java v1.3 and earlier.