You can assemble a Web archive (WAR) file that is enabled for Web
services from Java code with an assembly tool.
Before you begin
You can assemble Java-based Web services modules with assembly tools provided with WebSphere Application Server.
newfeatFor
Java API for XML-Based Web Services (JAX-WS) Web service applications, you
need the portable artifacts that are generated by the
wsgen command-line
tool when starting from a service endpoint implementation to complete this
task. The
wsgen tool processes a compiled service endpoint implementation
class as input and generates the following portable artifacts:
- any additional Java Architecture for XML Binding (JAXB) classes that are
required to marshal and unmarshal the message contents. The additional classes
include classes that are represented by the @RequestWrapper annotation and
the @ResponseWrapper annotation for a wrapped method.
- a WSDL file if the optional -wsdl argument is specified. The wsgen command
does not automatically generate the WSDL file. The WSDL file is automatically
generated when you deploy the service endpoint.
For Java API for XML-based RPC
(JAX-RPC) Web service applications, you need the following artifacts that
are generated by the
WSDL2Java command-line tool to complete this task:
- An assembled WAR file that contains the web.xml file, but is
not enabled for Web services.
- The Java class for the service endpoint interface
- A Web Services Description Language (WSDL) file
- The complete webservices.xml,ibm-webservices-bnd.xmi,
and ibm-webservices-ext.xmi deployment descriptors, and the Java
API for XML-based remote procedure call (JAX-RPC) mapping file classes that
are generated by the WSDL2Java command.