You can assemble
a web application 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.
For 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.
About this task
Assemble a web services-enabled WAR
file from Java code by following the actions
in the steps
for this task section.
Procedure
- Start an assembly
tool. Read about starting
the assembly tool in the Rational® Application Developer documentation.
- If you have not done so already, configure the assembly
tool so that it works on Java EE modules. You need to make sure that
the Java EE and Web categories are enabled. Read
about configuring the assembly tool in the Rational Application Developer documentation.
- Import the JavaBeans implementation
and the artifacts generated by the command-line tooling into the assembly
tool.
- Migrate WAR files created with the Assembly
Toolkit, Application
Assembly Tool (AAT) or a different tool to the Rational Application Developer assembly tool. To migrate
files, import your WAR files to the assembly tool. Read about migrating
code artifacts to an assembly tool in the Rational Application Developer information.
Results
The artifacts required to enable the web module for
web services
are added to the WAR file.
What to do next
Now you can assemble the
WAR file that is enabled for Web
services into an EAR file. To learn more, read about assembling a
web services-enabled WAR into an EAR file.