Use the wsdeploy command to add WebSphere® product-specific deployment classes to a web services-compatible enterprise application enterprise archive (EAR) file or an application client Java archive (JAR) file.
The wsdeploy command is supported by Java API for XML-based RPC (JAX-RPC) applications. The Java API for XML-Based Web Services (JAX-WS) programming model that is implemented by the application server does not support the wsdeploy command. If your web services application contains only JAX-WS endpoints, you do not need to run the wsdeploy command, as this command is used to process only JAX-RPC endpoints.
When the generated files are compiled, they can reference application-specific classes outside the EAR or JAR file, if the EAR or JAR file is not self-contained. In this case, use either the -jardir or -cp option to specify additional JAR or compressed files to be added to CLASSPATH variable when the generated files are compiled.
wsdeploy Input_filename Output_filename [options]
Specifies the path to the EAR or JAR file to deploy.
Specifies the path of the deployed EAR or JAR file. If output_filename already exists, it is silently overwritten. The output_filename can be the same as the input_filename.
Specifies a directory that contains JAR or compressed files. All JAR and compressed files in this directory are added to the CLASSPATH used to compile the generated files. This option can be specified zero or more times.
Specifies entries to add to the CLASSPATH when the generated classes are compiled. Multiple entries are separated the same as they are in the CLASSPATH environment variable.
Specifies to generate but not compile deployment code. This option implicitly specifies the -keep option.
Includes debugging information when compiling, that is, use javac -g to compile.
Displays a help message and exit.
Do not stop deployment if validation or compilation errors are encountered.
Do not delete working directories containing generated classes. A message is displayed indicating the name of the working directory that is retained.
Do not validate the web services deployment descriptors in the input file.
Displays processing information, including the names of the generated files.
Sets the JDK level for compiler compliance. Valid values include: 1.4, 5.0, 6.0 (default) and 7.0. This flag is optional.
wsdeploy x.ear x_deployed.ear -trace -keep
Processing web service module x_client.jar.
Keeping directory: f:\temp\Base53383.tmp for module: x_client.jar.
Parsing XML file:f:\temp\Base53383.tmp\WarDeploy.wsdl
Generating f:\temp\Base53383.tmp\generatedSource\com\test\WarDeploy.java
Generating f:\temp\Base53383.tmp\generatedSource\com\test\WarDeployLocator.java
Generating f:\temp\Base53383.tmp\generatedSource\com\test\HelloWsBindingStub.java
Compiling f:\temp\Base53383.tmp\generatedSource\com\test\WarDeploy.java.
Compiling f:\temp\Base53383.tmp\generatedSource\com\test\WarDeployLocator.java.
Compiling f:\temp\Base53383.tmp\generatedSource\com\test\HelloWsBindingStub.java.
Done processing module x_client.jar.
Option f was not recognized as a valid option.
Options can be abbreviated, but the abbreviation must be unique. In this case, the wsdeploy command cannot determine which option was intended.
A required parameter for an option is omitted.
A required option is omitted.