Network Deployment (Distributed operating systems), v8.0 > Reference > Command-line utilities
wsgen command for JAX-WS applications
The wsgen command-line tool generates the necessary artifacts required for Java API for XML Web Services (JAX-WS) applications when starting from Java code. The generated artifacts are Java 5 compliant, making them portable across different Java versions and platforms.
When using a bottoms-up approach to develop JAX-WS web services and you are starting from a service endpoint implementation, use the wsgen tool to generate the required JAX-WS artifacts.
The wsimport, wsgen, schemagen and xjc command-line tools are not supported on the z/OS platform. This functionality is provided by the assembly tools provided with WAS running on the z/OS platform. Read about these command-line tools for JAX-WS applications to learn more about these tools.
WAS provides Java API for XML-Based Web Services (JAX-WS) and Java Architecture for XML Binding (JAXB) tooling. The wsimport, wsgen, schemagen and xjc command-line tools are located in...
WAS_HOME\bin\Similar tooling is provided by the Java SE Development Kit (JDK) 6. On some occasions, the artifacts generated by both the tooling provided by WAS and the JDK support the same levels of the specifications. In general, the artifacts generated by the JDK tools are portable across other compliant runtime environments. However, it is a best practice to use the tools provided with this product to achieve seamless integration within the WAS environment and to take advantage of the features that may be only supported in WAS.
To take advantage of JAX-WS and JAXB V2.2 tooling, use the tools provided with the application server that are located in the WAS_HOME\bin\ directory.
The wsgen tool accepts a properly annotated service endpoint implementation using the @WebService annotation as input and generates the following artifacts:
- any additional Java Architecture for XML Binding (JAXB) classes that are required to marshal and unmarshal the message contents.
- a WSDL file if the optional -wsdl argument is specified. The wsgen tool does not automatically generate the WSDL file.
When using JAX-WS V2.2 tools, java.lang.RuntimeException and java.rmi.RemoteException references and their subclasses are no longer mapped in the WSDL file. This behavior change complies with the JAX-WS V2.1 specification conformance rule described in section 3.7 of the specification. This conformance rule specifies that the java.lang.RuntimeException and java.rmi.RemoteException classes and their subclasses cannot be treated as service-specific exceptions and mapped in the WSDL file.
In addition to using the tools from the command line, you can invoke these JAX-WS tools from within the Ant build environments. Use the com.sun.tools.ws.ant.WsGen Ant task from within the Ant build environment to invoke the wsgen tool. To function properly, this Ant task requires that you invoke Ant using the ws_ant script. The wsgen command does not differentiate the XML namespace between multiple XMLType annotations that have the same @XMLType name defined within different Java packages. When this scenario occurs, the following error is produced:
Error: Two classes have the same XML type name .... Use @XmlType.name and @XmlType.namespace to assign different names to them...This error indicates we have class names or @XMLType.names that have the same name, but exist within different Java packages.
To prevent this error, add the @XML.Type.namespace class to the existing @XMLType annotation to differentiate between the XML types.
(Solaris) 
Beginning with Sun and HP JDK Version 1.6 containing JAX-WS tooling v2.1.6, the behavior of the JAX-WS
runtime environments and tooling has changed in how it determines
which methods are exposed as web services operations in an effort
to better adhere to the JAX-WS specifications. Applications that might be affected by this change include web services applications that do not specify a WSDL file or an explicit service endpoint interface
(SEI).
To learn more, see the exposing methods in SEI-based JAX-WS web services information.
With JAX-WS applications, the wsgen command-line tool might not locate shared class files. We can specify the location of these class files using the com.ibm.websphere.webservices.wsdl_generation_extra_classpath custom property. See the documentation about the Java virtual machine custom properties.
The command-line syntax is:
(Windows)
WAS_HOME\bin\wsgen.bat [options] service_implementation_class(AIX)
(Solaris)
WAS_HOME/bin/wsgen.sh [options] service_implementation_class
Parameters
The service_implementation_class name is the only parameter that is required. The following parameters are optional for the wsgen command:
-service name "{http://mynamespace/}MyService"
-portname "{http://mynamespace/}MyPort"
Assembly tools
Exposing methods in SEI-based JAX-WS web services
Develop JAX-WS web services with annotations
Generate Java artifacts for JAX-WS applications
Implement web services applications with JAX-WS
Related
wsimport command for JAX-WS applications
Java virtual machine custom properties
Web services specifications and APIs
Java API for XML Web Services (JAX-WS) API documentation
Java API for XML Web Services (JAX-WS) 2.2 Tools Reference implementation