sun.com | docs.sun.com |  | How To Buy | My Sun | Worldwide Sites |

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Application Server Utility | wsdeploy(1)

- NAME
- SYNOPSIS
- DESCRIPTION
- OPTIONS
- EXAMPLES
- SEE ALSO

## NAME

> wsdeploy - reads a `WAR` file and the `jaxrpc-ri.xml` file and generates another `WAR` file that is ready for deployment

## SYNOPSIS

> `wsdeploy` [options] `input-WAR-file`

## DESCRIPTION

> Use the `wsdeploy` command to take a WAR file which does not have implementation specific server side tie classes to generate a deployable WAR file that can be deployed on the application server. `wsdeploy` internally runs `wscompile` with the -gen:server option. The `wscompile` command generates classes and a WSDL file which `wsdeploy` includes in the generated WAR file.

## OPTIONS

> -classpath path

>   location of the input class files.

> -keep

>   keep temporary files.

> -tmpdir

>   temporary directory to use.

> -o output WAR file

>   required; location of the generated WAR file.

> -verbose

>   outputs messages about what the compiler is doing.

> -version

>   prints version information.

## EXAMPLES

> The input WAR file for `wsdeploy` will typically have the following structure:

> >     META-INF/
> >     MANIFEST.MF
> >     WEB-INF/
> >         web.xml (normal deployment descriptor)
> >         jaxrpc-ri.xml
> >         <modelfile>.Z (optional model file generated using wscompile with -model option)
> >     classes/
> >                  Your application

> Running `wsdeploy` on the above WAR file results in the following actions:

> >     web.xml
> >         Renames to web-before.xml
> >         Adds elements: listener, servlet, and servlet-mapping
> >     jaxrpc-ri.xml
> >         renames to jaxrpc-before.xml
> >         writes jaxrpc-runtime.xml
> >             A list of endpoints containing: name, interface, implementation, tie, model, WSDL, service,
> >     port, and URL pattern attributes
> >     Generates classes and WSDL using wscompile -gen:server
> >     Packages the output.war file

> Example 1. Creating the output WAR file

> > >     wsdeploy -o Hello.war Input.war

> > Where the deployable WAR file `Hello.war` is generated.

> > The contents of the `Input.war` for a simple Hello web service would be:

> > `META-INF/MANIFEST.MF`

> > `WEB-INF/classes/hello/HelloIF.class`

> > `WEB-INF/classes/hello/HelloImpl.class`

> > `WEB-INF/jaxrpc-ri.xml`

> > `WEB-INF/web.xml`

> > Where:

> > `HelloIF` is the service's RMI interface

> > `HelloImpl` is the class that implements the interface

> > `web.xml` file is the deployment descriptor of a web component

> > The contents of the `jaxrpc-ri.xml` file would be:

> > `<?xml version="1.0" encoding="UTF-8"?>`

> > `<webServices`

> > `xmlns="http://java.sun.com/xml/ns/jax-rpc/ri/dd"`

> > `version="1.0"`

> > `targetNamespaceBase="http://com.test/wsdl"`

> > `typeNamespaceBase="http://com.test/types"`

> > `urlPatternBase="/ws">`

> > `<endpoint`

> > `name="MyHello"`

> > `displayName="HelloWorld Service"`

> > `description="A simple web service"`

> > `interface="hello.HelloIF"`

> > `implementation="hello.HelloImpl"/>`

> > `<endpointMapping`

> > `endpointName="MyHello"`

> > `urlPattern="/hello"/>`

> > `</webServices>`

## SEE ALSO

> `wscompile`(1M)

Sun Java System Application Server | Go To Top | Last Changed 29 Dec 2003

Company Info | Contact | Copyright 2004 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms.