WAS v8.5 > Develop applications > Develop web services > Assemble web services applications > Assemble web services applications

Assemble a web services-enabled WAR file from a WSDL file

We can assemble a WAR file from a Web Services Description Language (WSDL) file that is enabled for web services.

We can assemble Java-based web services modules with assembly tools provided with WebSphere Application Server.

For JAX-WS web service applications, you need the portable artifacts that are generated by the wsimport command-line tool when starting from a WSDL file to complete this task. The wsimport tool processes a WSDL file as input and generates the following portable artifacts:

• Service Endpoint Interface (SEI)
• Service class
• Exception classes that are mapped from the wsdl:fault class (if any)
• JAXB generated type values which are Java classes mapped from XML schema types

We can package the generated artifacts in a WAR file with the WSDL file and schema documents along with the endpoint implementation to deploy.

For 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 containing the EJB implementation, all the classes that generate from the WSDL2Java command-line tool and the web.xml deployment descriptor file.
• A 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.

Assemble a web services-enabled WAR file from a WSDL file by following the actions in the steps for this task section.

1. Start an assembly tool. Read about starting the assembly tool in the Rational Application Developer documentation.

2. If we have not done so already, configure the assembly tool so that it works on Java EE modules. You need to verify the Java EE and Web categories are enabled. Read about configuring the assembly tool in the Rational Application Developer documentation.
3. Import the JavaBeans implementation and the artifacts generated by the command-line tooling into the assembly tool.
4. Migrate JAR files created with the Assembly Toolkit, Application Assembly Tool or a different tool to the Rational Application Developer assembly tool. To migrate files, import your JAR 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 is added to the WAR file.

Now we 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.

Related concepts:

Development and assembly tools

Related

Assemble a web services-enabled WAR into an EAR file
Assemble a WAR file that is enabled for web services from Java code

Reference:

WSDL2Java command for JAX-RPC applications

+

Search Tips   |   Advanced Search