rmi2iiop - The RMI to IIOP Stub Compiler

rmi2iiop generates IIOP stubs and skeletons for CORBA objects expressed using Java RMI.

SYNOPSIS

rmi2iiop [-options] pacakage-qualified-class-name(s)

where options include:
    -help           print out this message
    -J<runtime flag>       Pass argument to the java interpreter
    -classpath <directories separated by colons>
                    list directories in which to look for classes
    -ds <directory> root destination directory for stubs/skels
    -poa            generate stubs and skels to be used with POA
    -multicast      generate stub/skels for Multicast Invocations
    -nostub         do not generate the stubs
    -noskel         do not generate the skeletons
    -notie          do not generate the TIE based skeletons
    -nolocal        do not enable stubs for local invocation
    -localnocopy    do not copy parameters on local invocation
    -keep           do not delete generated source files
    -keepgenerated  same as -keep
    -nocompile      do not compile the generated source files
    -verbose        turn verbose mode on
java-compiler options:
    -classpath <directories separated by colons>
                    list directories in which to look for classes
    -d <directory>  destination directory for classes
    -g              enable generation of debugging information
    -O              generate optimized code
    -depend         make compiler consider compiling dependencies
    -nowarn         turns off warning by the Java compiler

DESCRIPTION

The rmi2iiop compiler generates stub and skeleton class files for remote objects from the names of compiled Java classes that contain remote object implementations or interfaces. The classes named in the rmi2iiop command must be classes that have been compiled successfully with the javac command and must be fully package qualified. You can generate stubs/skeletons to be used with POA, or to be used with the PortableRemoteObject APIs.

OPTIONS

-help

Print the command line syntax and a short description of the compiler options.

-JruntimeFlag

Used to pass runtime flags to the Java interpreter/runtime. For example, in conjunction with the -D option, it sets a Java System property. Muliple -J arguments can be used to specify more than one runtime flags.

-classpath path

Specifies the classpath where rmi2iiop looks for classes. It is not necessary to specify the JDK or the ORB classes here. The elements in the path must be separeted by platform specific path separator.

-ds directory

Specifies the root directory of the generated Java source. The current directory is the default value for directory.

-poa

Specifies that the generated skeletons should work with the Portable Object Adapter (POA).  POA skeletons extend org.omg.PortableServer.Servant class.

If -poa is not specified, then the generated skeletons can only be used to write simple transient objects using the javax.rmi.PortableRemoteObjectAPIs. These skeletons extend javax.rmi.CORBA.Stub.

-multicast

Specifies that the compiler should generate stubs and skeletons for Multicast Object Invocations. The -poa and -multicast options are mutually exclusive.

-nostub

Specifies that the stub should not be generated.

-noskel

Specifies that the skeletons should not be generated.

-notie

Specifies that delegation based skeletons should not be generated.

-nolocal

Specifies that the generated stubs should not be enabled for local invocation. The serializable parameters are deep copied (see -localnocopy option) and the servant is directly invoked. The local stubs are designed such that the object adapter gets an opportunity to enfore its rules and behavior. For example the Portable Object Adapter can activate POA instances, observe POA Manager state machine rules, and activate servant objects using the user supplied servant manager.

-localnocopy

Specifies that the serializable parameters should not be copied on local invocation. Note, that this is a violation of the RMI parameter passing semantics but the option is provided for performance trade offs.

-keep
-keepgenerated

Do not delete the generated code after compilation.

-nocompile

Specifies that the generated Java code should not be compiled. See Java compiler options.

-verbose

Put the rmi2iiop compile in verbose mode. It prints out the class files it is reading and the Java files it is generating.

JAVA Compiler Options

-classpath path

Specifies the classpath where rmi2iiop looks for classes. It is not necessary to specify the JDK or the ORB classes here. The elements in the path must be separeted by platform specific path separator.

-d directory

Specifies the root directory of the class file hierarchy. In other words, this is essentially a destination directory for your compiled classes. The current directory is the default value for directory.

-g

Enables generation of debugging tables. Debugging tables contain information about line numbers and local variables - information used by Java debugging tools. By default, only line numbers are generated, unless optimization (-O) is turned on.

-O

Directs the compiler to try to generate faster code by inlining static, final and private methods. This option may slow down compilation, make larger class files, and/or make it difficult to debug.

-depend

Makes the compiler consider recompiling classes which are referenced from other classes. Normally, it only recompiles missing or out-of-date classes that are referred to from source  code.

-nowarn

Turns off warnings. If used the Java compiler does not print out any warnings.

EXAMPLES

• Generate and compile POA binding for helloWorld.HelloImpl remote implementation.

    rmi2iiop helloWorld.HelloImpl
 
• Generate and compile POA bindings for helloWorld.Hello remote interface. Make the Java compiler output go to directory dir1 and the source output go to directory dir.

    rmi2iiop -poa -ds dir2 -d dir1 helloWorld.Hello

SEE ALSO

idl2java, rmi2idl
 

---

Copyright © 1998-2003, Novell, Inc. All rights reserved.