Java Remote Method Invocation: 5 - Server Interfaces - JDK 5 Documentation v1.2.2, Java 2 SDK 英文文档

Java Remote Method Invocation

5.11 Stub and Skeleton Compiler

The rmic stub and skeleton compiler is used to compile the appropriate stubs and skeletons for a specific remote object implementation. The compiler is invoked with the package qualified class name of the remote object class. The class must previously have been compiled successfully.

The location of the imported classes may be specified either with the CLASSPATH environment variable or with the -classpath argument.

The compiled class files are placed in the current directory unless the -d argument is specified.

The -keepgenerated (or -keep) argument retains the generated java source files for the stubs and skeletons.

The stub protocol version can also be specified:

-v1.1 creates stubs/skeletons for the JDK 1.1 stub protocol version

-vcompat (the default in JDK 1.2) creates stubs/skeletons compatible with both JDK 1.1 and 1.2 stub protocol versions

-v1.2 creates stubs for JDK 1.2 stub protocol version only (note thatskeletons are not needed for the JDK 1.2 stub protocol)

The -show option displays a graphical user interface for the program.

Most javac command line arguments are applicable (except -O) and can be used with rmic:

-g generates debugging info

-depend recompiles out-of-date files recursively

-nowarn generates no warnings

-verbose outputs messgaes about what the compiler is doing

-classpath <path> specifies where to find input source and class files

-d <directory> specifies where to place generated class files

-J<runtime flag> passes the argument to the java interpreter

CONTENTS | PREV | NEXT