rmi2soap is the jBroker Web RMI to SOAP compiler.
rmi2soap [options] package-qualified-class-name(s)where options include:
-help print out this message
-J<vm flag> pass argument to the java interpreter
-classpath <path> specify where to find user class files
-ds <directory> destination directory for generated source files
-xsd <uri> specify the XML Schema URI
-xmlns <ns> specify the XML namespace for the interface
-addr <url> specify the binding for the service
-literal literal use (default is encoded)
-document document style (default is rpc)
-transport <uri> specify the transport URI
-action <uri> specify the encodingStyle
-encoding <uri> specify the soapAction URI
-nostub do not generate the stubs
-noskel do not generate the skeletons
-notie do not generate the TIE based skeletons
-noserv do not generate the service interfaces
-typemapping <file> load type mappings from file
-nomarshalers do not generate marshalers
-keep do not delete generated source files
-keepgenerated same as -keep
-nocompile do not compile the generated source files
-verbose turn verbose mode on
-wsdllocation <url> the URL to be returned by getWSDLDocumentLocation()
-genclient generate a sample client for the web service
-gencallclient generate a call based sample client for the web service
-genserver generate a sample server for the web service
java-compiler options:
java-compiler options:
-classpath <path> specify where to find user class files
-d <directory> destination directory for classes
-g enable generation of debugging information
-O generate optimized code
-depend make compiler consider compiling dependencies
-nowarn generate no warnings from Java compiler
The rmi2soap compiler transforms Java remote interfaces (RMI) into SOAP stubs and skeletons. This compiler is typically used by developers who need stubs and skeletons to call or implement a Web Service based on Java RMI. If the WSDL is available, developers will often prefer to use the wsdl2java compiler.
-helpPrints out the command syntax.-J<vm flag>Pass a flag to the jvm. As an example -J-Xms100m sets the maximum heap size to 100 MB when running rmi2soap.-classpathSet the classpath available to the java compiler (javac) when compiling the generated Java files.-ds <directory>Output generated Java files to the specified directory. The directory will automatically be created if it doesn't exist. This option only has meaning when used in conjunction with the -keep option.-xsd <uri>Use uri as the XML Schema string in outgoing SOAP messages. The default value is "http://www.w3.org/1999/XMLSchema".-xmlns <ns>Use ns as the targetNamespace in SOAP messages produced by the generated stubs and skeletons. Method names and parameter names are scoped to this namespace when SOAP messages goes on the wire.-addr <url>The default binding address for stubs. When using this option, the generated stub will by default invoke on the Web Service located at this address.-literalMake the use of messages in the SOAP bindings literal instead of encoded. By default, the rmi2soap compiler will generate encoded message definitions.-documentMake the binding style document instead of rpc. By default, the rmi2wsdl compiler will generate an rpc style SOAP binding.-transport <uri>Use the specified transport URI.-action <uri>Use the specified soap action URI for all methods.-encoding <uri>Use the specified encoding style URI.-nostubInstruct the compiler not to generate stubs. This options is typically used by developers who only wish to implement a Web Service, but do not require calling said Web Service.-noskelInstructs the compiler not to generate skeletons. This option is typically used by developers who are implementing Web Services client applications, but do not need to implement the Web Service itself.-notieInstruct the compiler not to generate tie classes. Tie classes are also used by Web Service developers and is an advanced server-side construct that allows delegation to another Java class.-noservInstruct the rmi2soap compiler not to generate service classes. This option can be used for server-side implementations that don't use the service interface.-typemapping <file>Load type mappings from file. This argument can be specified multiple times.-nomarshalersInstruct the rmi2soap compiler not to generate marshaler classes.-keepKeep the source files generated by the rmi2soap compiler. Typically, developers will not need the generated stub and skeleton source files so the default behavior is to delete those files.-keepgeneratedSame as -keep.-nocompileDo not compile generated Java source into class files. This option is typically used with the -keep option.-verbosePrint out details about the compilation.-wsdllocation <url>Specify the URL to be returned by the getWSDLDocumentLocation() method of the Service.-genclientThis flag will cause the wsdl2java compiler to generate a sample client, which can be used to invoke the Web Service(s) defined in the WSDL document.-gencallclientThis flag will cause the wsdl2java compiler to generate a sample client that uses the call API, which can be used to invoke the Web Service(s) defined in the WSDL document.-genserverThis flag will cause the wsdl2java compiler to generate a sample server implementation of the Web Service(s) defined in the WSDL document.
-classpathSet the classpath available to the java compiler (javac) when compiling the generated Java files.-d <directory>Set the output directory for compiled class files. The directory will automatically be created if it doesn't exist. Depending on the package of the source file additional directories may be created below this directory.-gEnables generation of debugging information.-OGenerates optimized code.-dependMake the javac compiler consider dependencies.-nowarnDo not generate warning messages from the javac compiler.
Copyright © 2001-2002, SilverStream Software, Inc. All rights reserved.