If you execute the cjwsimport command, the Java source, such as a service class, required for Web Service client development is generated. For the cjwsimport command, see 14.1 cjwsimport command.

The following is an execution example when developing Web Service clients in the same environment in which the Web Service is developed:

> cd c:\temp\jaxws\works\fromwsdl\client\
> mkdir src/
> mkdir classes/
> "%COSMINEXUS_HOME%\jaxws\bin\cjwsimport.bat" -s src -d classes ..\server\WEB-INF\wsdl\input.wsdl

The following is an execution example when developing Web Service clients on an environment different from the environment in which the Web Service is developed:

> cd c:\temp\jaxws\works\fromwsdl\client\
> mkdir src/
> mkdir classes/
> "%COSMINEXUS_HOME%\jaxws\bin\cjwsimport.bat" -s src -d classes http://webhost:8085/fromwsdl/TestJaxWsService?wsdl

When the execution is successful, the Java source will be generated in c:\temp\jaxws\works\fromwsdl\client\src\com\example\sample\directory. The directory path com\example\sample\(directory-path-corresponding-to-the-package) changes as per the coding of the namespace URI. For the mapping between namespace URIs and packages, see 15.1.1 Mapping a namespace to a package name.

The following table lists and describes the products:

Table 4-4 Products during service class generation (Starting from WSDL)

The file names JaxWsTest1, TestJaxWs, and TestJaxWsService change according to the coding of the local name for operation, local name for port type, and local name for services. For the mapping between a local name for operation, local name for port type, and local name for services and Java sources, see the following sections:

• 15.1.2 Mapping a port type to a SEI name
• 15.1.3 Mapping an operation to a method name
• 15.1.4 Mapping a message part to a parameter and return value (For wrapper style)
• 15.1.5 Mapping the message part to the parameter and return value (For non-wrapper style)