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

The following is an example when the Web Service client is developed in the same environment as the Web Service:

> cd c:\temp\jaxws\works\wsrm\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 example when the Web Service client is developed in an environment other than the Web Service:

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

On successful termination of the cjwsimport command, the Java sources are generated in the c:\temp\jaxws\works\wsrm\client\src\com\example\sample\ directory. Note that the directory path com\example\sample\ (the directory path corresponding to the package) changes according to the coding of the namespace URI. For the mapping between Namespace URI and package, see 15.1.1 Mapping a names pace to a package name.

The following table lists the generated products:

Table 35-4 Products created when the service class is generated (Starting from WSDL)

The file names JaxWsTest1, TestJaxWs, and TestJaxWsService change according to the coding of the local name for the operation, the local name for the port type, and the local name for the services. For the mapping between the local name for the operation, the local name for the port type, and the local name for the 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 a message part to a parameter and return value (For non-wrapper style)