## Name

wsimport - Java(TM) API for XML Web Services (JAX-WS) 2.0

f3Specification Version: 2.1
f3Implementation Version: 2.1.1

## Overview

The f2wsimport tool generates JAX-WS portable artifacts, such as:

o Service Endpoint Interface (SEI)

o Service

o Exception class mapped from wsdl:fault (if any)

o Async Reponse Bean derived from response wsdl:message (if any)

o JAXB generated value types (mapped java classes from schema types)

These artifacts can be packaged in a WAR file with the WSDL and schema documents along with the endpoint implementation to be deployed. also provides wsimport ant task, see

f2Wsimport ant task @

https://jax-ws.dev.java.net/nonav/2.1.1/docs/wsimportant.html.

## Launching wsimport

o f3Solaris/Linux

* f2/bin/wsimport.sh -help

o f3Windows

* f2\bin\wsimport.bat -help

## Syntax

    f3
    wsimport [options] <wsdl>

The following table lists the f2wsimport options.

    Specify where to place generated output files

    Specify external JAX-WS or JAXB binding files (Each f2<file> must have its own f2-b)

    Pass this option to JAXB schema compiler

    Specify catalog file to resolve external entity references, it supports TR9401, XCatalog, and OASIS XML Catalog format. Please read the documentation of
    f2catalog @

https://jax-ws.dev.java.net/nonav/2.1.1/docs/catalog-support.html and see f3catalog sample.

Allow vendor extensions (functionality not specified by the specification). Use of extensions may result in applications that are not portable or may not interoperate with other implementations

f3-httpproxy:<host>:<port>

Specify an HTTP proxy server (port defaults to 8080)

Specifying a target package via this command-line option, overrides any wsdl and schema binding customization for package name and the default package name algorithm defined in the specification

Specify where to place generated source files

Output messages about what the compiler is doing

Print version information

f3-wsdllocation <location>

f2@WebServiceClient.wsdlLocation value

Generate code as per the given JAX-WS specification version. version 2.0 will generate compliant code for JAX-WS 2.0 spec.

##

    h'|n(40u'f3Optionh'|n(41u'f3Description
    h'|n(40u'f3-d <directory> h'|n(41u'
    h'|n(40u'f3-b <path> h'|n(41u'
    h'|n(40u'f3-B <jaxbOption>h'|n(41u'
    h'|n(40u'f3-catalogh'|n(41u'
    h'|n(40u'f3-extension h'|n(41u'
    h'|n(40u'f3-help h'|n(41u'Display help
    h'|n(40u'h'|n(41u'
    h'|n(40u'f3-keep h'|n(41u'Keep generated files
    h'|n(40u'f3-p h'|n(41u'
    h'|n(40u'f3-s <directory> h'|n(41u'
    h'|n(40u'f3-verbose h'|n(41u'
    h'|n(40u'f3-version h'|n(41u'
    h'|n(40u'h'|n(41u'
    h'|n(40u'f3-target h'|n(41u'
    h'|n(40u'f3-quiet h'|n(41u'Suppress wsimport output
    Multiple JAX-WS and JAXB binding files can be specified using f2-b option and they can be used to customize various things like package names, bean names, etc. More information on JAX-WS and JAXB binding files can be found in the
    f2customization documentation @

    https://jax-ws.dev.java.net/nonav/2.1.1/docs/customizations.html.
    The following table lists f2wsimport non-standard options:

    Map headers not bound to request or response message to Java method parameters.

    WSDL URI that specifies the file that contains authorization information; this URI is in the following format: http://f2<user name>:f2<password>@f2<host name>/f2<Web service name>?wsdl

    Print debugging information.

    f3-Xno-addressing-databinding

    Enable binding of W3C f2EndpointReferenceType to Java.

    Do not compile generated Java files.

    h'|n(40u'f3Optionh'|n(41u'f3Description
    h'|n(40u'f3-XadditionalHeadersh'|n(41u'
    h'|n(40u'f3-Xauthfile <file>h'|n(41u'
    h'|n(40u'f3-Xdebugh'|n(41u'
    h'|n(40u'h'|n(41u'
    h'|n(40u'f3-Xnocompileh'|n(41u'

    Example

    f3
    f3wsimport -p stockquote http://stockquote.example.com/quote?wsdl

    This will generate the Java artifacts and compile them by importing the f2http://stockquote.example.com/quote?wsdl.