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

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

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 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)
  • Java Architecture for XML Binding (JAXB) generated type values which are Java classes mapped from XML schema types
You can package the generated artifacts in a web application archive (WAR) file with the WSDL file and schema documents along with the endpoint implementation that you plan to deploy.
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 Enterprise JavaBeans (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.

About this task

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

Procedure

  1. Start an assembly tool. Read about starting the assembly tool in the Rational® Application Developer documentation.
  2. 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.
  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.

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.



In this information ...


Related concepts

IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic Task topic    

Terms of Use | Feedback

Last updatedLast updated: Sep 19, 2011 6:15:55 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=matt&product=was-express-dist&topic=twbs_assembwarwsdl
File name: twbs_assembwarwsdl.html