THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Commands | Description |
|---|---|
Display help information | |
Print arguments to STDOUT | |
Load a file or URL to the current shell | |
Clear the terminal screen | |
Set a variable | |
Unset a variable | |
Exit GShell | |
Start a server | |
Stop the server | |
Wait for the server to start | |
Start an application client | |
Connect to a Geronimo server | |
Save the username and password for this connection | |
Disconnect from a Geronimo server | |
Deploy a module | |
Redeploy a module | |
Undeploy a module | |
Distribute a module | |
Start a module | |
Restart a module | |
Stop a module | |
List modules | |
List targets | |
Install plug-ins into the server | |
Install library | |
Install a plug-in | |
Extract a Geronimo server from the current one | |
Create a new instance | |
Connect to a remote GShell server | |
Start a remote GShell server | |
Monitor cluster heartbeat | |
Administer cluster | |
Generate JAX-WS artifacts WSDL file from class | |
Generate JAX-WS artifacts from class | |
Generate JAX-WS artifacts from WSDL | |
Generate JAX-WS artifacts from WSDL |
...
| No Format |
|---|
geronimo/start-server -A <JAR> -D <name=value> -G <name=value> -H <dir> -J <flag> -P <name> -b -j <dir> -l <file> -m <module> -p <port> -q -t <time> -u <user> -v -w <password> --secure |
These commands options are described in the following table except the general options:
...
Monitoring cluster heartbeat
Administering cluster
Generating
...
WSDL file from class
The jaxws/java2ws command can be used to create JAX-WS artifacts from a Java class, and used to generate a WSDL file, wrapper bean, server side code and client side code from a Web service endpoint's implementation (SEI) class and associated types classes. It uses this syntax:
| No Format |
|---|
jaxws/java2ws -databinding <jaxb or aegis> -frontend <jaxws or simple> -wsdl -wrapperbean -client -server -ant -wrapperbean -o <output-file> -d <resource-directory> -s <source-directory> -classdir <compile-classes-directoty> -cp <class-path> -soap12 -t <target-namespace> -beans <pathname of the bean definition file> -servicename <service-name> -portname <port-name> -address <address> -createxsdimports -h -v -verbose -quiet <classname> |
The arguments used to manage the code generation process are reviewed These options are described in the following table.:
Option Interpretation
-help or -h | -help or -h | Can be used to obtain the help information. |
--databinding | -databinding <jaxb or aegis> | Can be used to specify the data binding (jaxb or aegis). By default it is jaxb for jaxws frontend, and aegis for simple frontend. |
-frontend | -frontend <jaxws or simple> | Can be used tp specify the frontend. Jaxws and the simple frontend are supported. |
-wsdl | -wsdl | Can be used to generate the WSDL file. |
-client | -client | Can be used to generate client side code. |
-server | -server | Can be used to generate server side code. |
-ant | -ant | Can be used to generate an Ant |
-wrapperbean | -wrapperbean | Can be used to generate the wrapper and fault bean. |
-o | -o <output-file> | Can be used to specify the name of the generated WSDL file. |
-d | -d <resource-directory> | Can be used to specify the directory in which the resource files are located. The wsdl file will be placed into this directory by default. |
-s | -s <source-directory> | Can be used to specify the directory in which the generated source files (wrapper bean ,fault bean ,client side or server side code) are located. |
-classdir | -classdir <compile-classes-directoty> | Can be used to specify the directory in which the generated sources are compiled into. If not specified, the files are not compiled. |
-cp | -cp <class-path> | Can be used to specify the SEI and types class search path of directories and zip/jar files. |
-soap12 | -soap12 | Can be used to indicate that the generated WSDL is to include a SOAP 1.2 binding. |
-t | -t <target-namespace> | Can be used to specify the target namespace to use in the generated WSDL file. |
-beans | -beans <pathname of the bean definition file> |
|
-servicename | -servicename <service-name> | Can be used to specify the value of the generated service element's name attribute. |
-portname | -portname <port-name> | Can be used to specify the port name to use in the generated WSDL. |
-address | -address <address> |
|
-createxsdimports | -createxsdimports | Can be used to output schemas to separate files and load them by imports instead of inlining them into the wsdl. |
-v | -v | Can be used to obtain the version number. |
-verbose | -verbose | Can be used to display comments during the code generation process. |
-quiet | -quiet | Can be used to suppress comments during the code generation process. |
<classname> | <classname> | Can be used to specify the name of the SEI class. |
Generating JAX-WS artifacts from class
The jaxws/wsgen command can be used to create generate necessary portable artifacts for JAX-WS artifacts applications from a Java class, and Java classes. Unlike jaxws/java2ws, this command generates a WSDL file only when requested. It uses this syntax:
| No Format |
|---|
jaxws/wsgen -classpath <path> -cp <path> -d <directory> -extension -help -keep -r <directory> -verbose -version -wsdl[:protocol] -servicename <name> -portname <name> |
The arguments used to manage the code generation process are reviewed These options are described in the following table.:
-classpath or -cp | -classpath <path> or -cp <path> | Can be used to specify the location of the service implementation class. | ||
-d | -d <directory> | Can be used to specify where to place the directory in which the generated output files will be placed. | ||
-extension | -extension | Can be used to allow custom extensions for functionality not specified by the JAX-WS specification. Use of the extensions can result in applications that are not portable or do not interoperate with other implementations. Here is a list of the extentions available:
| ||
-help | -help | Can be used to obtain the help information. | ||
-keep | -keep | Can be used to keep the generated source files. | ||
-r | -r <directory> | Can be used to specify the directory in which generated WSDL file is placed. This parameter is only used in conjunction with the -wsdl parameter. | ||
-verbose | -verbose | Can be used to output messages about what the compiler is doing. | ||
-version | -version | Can be used to obtain the version number. If you specify this option, only the version information will be output and normal command processing will not occur. | ||
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="d32c27a10321135e-84fd79ba-40a645c4-a07b8fbe-15e990deaf793ce50e162252"><ac:plain-text-body><![CDATA[ | -wsdl | -wsd [:protocol] | Can be used to force direct wsgen to generate a WSDL file and is typically used by a developer to review a WSDL file before the endpoint is deployed. By default, wsgen does not generate a WSDL file. The protocol is optional and specifies can be used to specify the protocol used in the wsdl:binding, and is optional. Valid values for protocol are soap 1.1 and Xsoap 1.2. The default value is soap 1.1. The Xsoap 1.2 value can only be used in conjunction with the | ]]></ac:plain-text-body></ac:structured-macro> |
-servicename | -servicename <name> | Can be used to specify a wsdl:service name to be generated in the WSDL file. This parameter is only used in conjunction with the -wsdl option. |
...
| No Format |
|---|
jaxws/wsdl2java -fe <front-end-name>* -db <data-binding-name>* -wv <wsdl-version> -p <[wsdl-namespace = ]package-name>* -sn <service-name> -b <bindling-file-name> -catalog <catalog-file-name> -d <output-directory> -compile -classdir <compile-classes-directory> -impl -server -client -all -autoNameResolution -defaultValues<=class-name-for-DefaultValueProvider> -ant -nexclude <schema-namespace [=java=package- name]>* -exsh <<true,false>> -dns <<true,false>> -dex <<true,false>> -validate -keep -wsdllocation <wsdlLocation> -xjc <xjc-arguments> -noAddressBinding -h -v -verbose -quiet <wsdlurl> |
The arguments used to manage the code generation process are reviewed These options are described in the following table.:
Option | Usage | Description | ||
|---|---|---|---|---|
-help or -h | -help or -h | Can be used to obtain the help information. | ||
-fe | -fe <frontend-name> | Can be used to specify the frontend. By default it is JAXWS frontend. Currently only JAXWS frontend is supported. | ||
-db | -db <databinding-name> | Can be used to specify the data binding. By default it is jaxb. Currently only JAXB databinding is supported. | ||
-wv | -wv <wsdl-version> | Can be used to specify the wsdl version. By default it is WSDL1.1. Currently only WSDL1.1 version is supported. | ||
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="67fd32d0550d5e9a-1058ac0c-4ac1415b-8e2e998f-c3474f050a78f450baf7b31a"><ac:plain-text-body><![CDATA[ | -p | -p <[wsdl-namespace = ] package-name>* | Can be used to specify zero or more package names for the generated code. | ]]></ac:plain-text-body></ac:structured-macro> |
-sn | -sn <service-name> | Can be used to specify the WSDL service name for the generated code. | ||
-b | -b <bindling-file-name> | Can be used to specify zero , or more , JAXWS or JAXB binding files. Use You can use spaces to separate more than one entry. | ||
-catalog | -catalog <catalog-file-name> | Can be used to specify catalog file to map that maps the imported wsdl/schema. | ||
-d | -d <output-directory> | Can be used to specifies specify the directory into which the generated code files are written. | ||
-compile | -compile | Can be used to compile generated Java files. | ||
-classdir | -classdir <compile-classes-directory> | Can be used to specify the directory into which the compiled class files are written. | ||
-impl | -impl | Can be used to generate starting point code for an implementation object. | ||
-client | -client | Can be used to generate starting point code for a client mainline. | ||
-server | -server | Can be used to generate starting point code for a server mainline. | ||
-all | -all | Can be used to generate all starting point code: types, service proxy, service interface, server mainline, client mainline, implementation object, and an Ant | ||
-autoNameResolution | -autoNameResolution | Can be used to automatically resolve naming conflicts without requiring the use of binding customizations. | ||
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="d944590b61f29366-b6d1aa0d-45ed4e95-b9ee9efb-e6a20deab9115802c295adc8"><ac:plain-text-body><![CDATA[ | -defaultValues | -defaultValues=[DefaultValueProvider impl] | Can be used to generate default values for the impl and client. You can also provide a custom default value provider. The default provider is RandomValueProvider. | ]]></ac:plain-text-body></ac:structured-macro> |
-ant | -ant | Can be used to generates the Ant | ||
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="0cc1817db29fcf0a-b3e41e38-41264d34-bab795b2-17b5106733e5625310850d40"><ac:plain-text-body><![CDATA[ | -nexclude | -nexclude <schema-namespace [=java=package-name]>* | Can be used to ignore the specified WSDL schema namespace when generating code. This option may can be specified multiple times. Also, optionally specifies the Java package name used by types described in the excluded namespace(s) can also be specified. The java package name is optional. | ]]></ac:plain-text-body></ac:structured-macro> |
-exsh | -exsh <<true,false>> | Can be used to enable or disable processing of implicit SOAP headers (SOAP headers defined in the wsdl:binding but not wsdl:portType section.) By default it is false. | ||
-dns | -dns <<true,false>> | Can be used to enable or disable the loading of the default namespace package name mapping. Default is true and http://www.w3.org/2005/08/addressing=org.apache.cxf.ws.addressing namespace package mapping will be enabled. | ||
-dex | -dex <<true,false>> | Can be used to enable or disable the loading of the default excludes namespace mapping. Default is true. | ||
-validate | -validate | Can be used to enable validating the WSDL before generating the code. | ||
-keep | -keep | Can be used to indicate that the code generator will not overwrite any preexisting files. You will be responsible for resolving any resulting compilation issues. | ||
-wsdlLocation | -wsdllocation <wsdlLocation> | Can be used to specify the value of the @WebServiceClient annotation's wsdlLocation property. | ||
-xjc | -xjc <xjc-arguments> | Can be used to specify a comma separated list of arguments that are passed directly to the XJC processor when using the JAXB databinding. A list of available XJC plugins can be obtained using | ||
-noAddressBinding | -noAddressBinding | For compatibility with CXF 2.0, this flag directs Can be used to direct the code generator to generate the older CXF proprietary WS-Addressing types instead of the JAX-WS 2.1 compliant WS-Addressing types. | ||
-v | -v | Can be used to obtain the version number. | ||
-verbose | -verbose | Can be used to display comments during the code generation process. | ||
-queit | -quiet | Can be used to suppress comments during the code generation process. | ||
<wsdlurl> | <wsdlurl> | Can be used to specify the path and name of the WSDL file in generating the code. |
The jaxws/wsimport command can be used to create java classes from WSDL, and generates the required portable artifacts for JAX-WS Web service applications from an existing WSDL file. It uses this syntax:
| No Format |
|---|
jaxws/wsimport -b <path> -B <jaxBOption><jaxbOption> -catalog <file> -d <directory> -extension -help -httpproxy:<host>:<port> -keep -p <pkg> -quiet -s <directory> -target <version> -verbose -version -wsdllocation <location> |
The arguments used to manage the code generation process are reviewed These options are described in the following table.:
-d | <directory> | Can be used to specify where the generated output files are located. | -b | <path> | Can be used to specify the external JAX-WS or JAXB binding files. You can specify multiple JAX-WS and JAXB binding files by using the -b option; however, each file must be specified with its own -b option. |
-B | -B <jaxbOption> |
| |||
-catalog | -catalog <file> | Can be used to specify the catalog file to resolve that resolves external entity references. It supports the TR9401, XCatalog, and the OASIS XML Catalog formats. | |||
-d | <directory> | Can be used to specify the directory in which the generated output files are placed. | |||
-extension | -extension | Can be used to allow custom extensions for functionality that are not specified by the JAX-WS specification. The use of custom extensions can result in applications that are not portable or do not interoperate with other implementations | . | ||
-help | -help | Can be used to obtain the help information. | |||
-httpproxy | -httpproxy:<host>:<port> | Can be used to specify an HTTP proxy. The default port value is 8080. | |||
-keep | -keep | Can be used to keep the generated source files. | |||
-p | -p <pkg> | Can be used to specify a target package with this command-line option and overrides any WSDL file and schema binding customization for the package name and the default package name algorithm defined in the JAX-WS specification. | |||
-s | -s <directory> | Can be used to specify the directory in which the generated source files are placed. | |||
-target | -target <version> |
| |||
-verbose | -verbose | Can be used to output messages about what the compiler is doing. | |||
-version | -version | Can be used to obtain the version information. If you specify this option, only the version information is included in the output and normal command processing does not occur. | |||
-wsdlLocation | -wsdllocation <location> | Can be used to specify the @WebServiceClient.wsdlLocation value. |