| 1 |
779 |
jeremybenn |
The GNU Classpath tools are stored in the tools.zip. They can be invoked by
|
| 2 |
|
|
putting this archive into classpath and specifying the tool main class as the
|
| 3 |
|
|
class to run (parameters usually follow). The current release contains the
|
| 4 |
|
|
following tools:
|
| 5 |
|
|
|
| 6 |
|
|
== GIOP tools ==
|
| 7 |
|
|
|
| 8 |
|
|
GIOP tools are used for creating the applications that use GIOP communication
|
| 9 |
|
|
protocol. It provides necessary support for org.omg.* and javax.rmi.*
|
| 10 |
|
|
packages.
|
| 11 |
|
|
|
| 12 |
|
|
All GIOP tools support the --help option, for instance:
|
| 13 |
|
|
java -cp tools.zip gnu.classpath.tools.giop.IorParser --help
|
| 14 |
|
|
|
| 15 |
|
|
The list of the currently available GIOP tools (name matches the main
|
| 16 |
|
|
class in gnu.classpath.tools.giop package):
|
| 17 |
|
|
|
| 18 |
|
|
* GRMIC - RMI-IIOP stub and tie generator.
|
| 19 |
|
|
* NameService - GIOP transient naming service (this tool is called
|
| 20 |
|
|
tnameserv in Sun's package).
|
| 21 |
|
|
* NameServicePersistent
|
| 22 |
|
|
- GIOP persistent naming service (this tool is called
|
| 23 |
|
|
orbd in Sun's package).
|
| 24 |
|
|
* IorParser - Parses the stringified form of the interoperable
|
| 25 |
|
|
object references (IOR's).
|
| 26 |
|
|
|
| 27 |
|
|
== RMI tools ==
|
| 28 |
|
|
|
| 29 |
|
|
RMI tools provide support for java.rmi package. All tools support
|
| 30 |
|
|
the --help key by printing more information, for instance:
|
| 31 |
|
|
java -cp tools.zip gnu.classpath.tools.rmi.RMIC --help
|
| 32 |
|
|
|
| 33 |
|
|
The list of the currently available RMI tools (name matches the main tool class
|
| 34 |
|
|
in gnu.classpath.tools.rmi package):
|
| 35 |
|
|
|
| 36 |
|
|
* RMIC - RMI stub and tie source code generator (complements
|
| 37 |
|
|
the ASM based bytecode generator in the separate
|
| 38 |
|
|
cp-tools project). This tool is only needed for
|
| 39 |
|
|
research and backward-compatibile applications, as
|
| 40 |
|
|
Classpath supports the 1.5 feature to replace such
|
| 41 |
|
|
stubs by proxy classes.
|
| 42 |
|
|
* REGISTRY - The persistent RMI naming service.
|
| 43 |
|
|
* RMID - The persistent RMI activation daemon, supports the
|
| 44 |
|
|
java.rmi.activation package.
|
| 45 |
|
|
|
| 46 |
|
|
== Security tools ==
|
| 47 |
|
|
|
| 48 |
|
|
Security tools (currently) are used for signing and verifying JAR files
|
| 49 |
|
|
as well as (planned) generating and managing cryptographic tokens and
|
| 50 |
|
|
credentials.
|
| 51 |
|
|
|
| 52 |
|
|
The list of individual tools, the name of their main class that should be
|
| 53 |
|
|
invoked by the Java launcher, and a summary of what they provide follows:
|
| 54 |
|
|
|
| 55 |
|
|
* jarsigner gnu.classpath.tools.jarsigner.Main
|
| 56 |
|
|
A drop-in replacement for the "jarsigner" tool.
|
| 57 |
|
|
|
| 58 |
|
|
|
