Implementing web services applications from existing WSDL files with JAX-RPC

You can develop a web service with an existing Web Services Description Language (WSDL) file using the Java API for XML-based RPC (JAX-RPC) programming model.

Before you begin

Best practice Best practice: IBM® WebSphere® Application Server supports the Java API for XML-Based Web Services (JAX-WS) programming model and the Java API for XML-based RPC (JAX-RPC) programming model. JAX-WS is the next generation web services programming model extending the foundation provided by the JAX-RPC programming model. Using the strategic JAX-WS programming model, development of web services and clients is simplified through support of a standards-based annotations model. Although the JAX-RPC programming model and applications are still supported, take advantage of the easy-to-implement JAX-WS programming model to develop new web services applications and clients. bprac

Locate the WSDL file that defines the web service that you want to implement. You can develop a WSDL or obtain one from an existing web service through email, downloading or a Uniform Resource Locator (URL).

About this task

To develop web services based on the JAX-RPC programming model, you can use a bottom-up development approach starting from existing JavaBeans or enterprise beans or you can use a top-down development approach starting with an existing Web Services Description Language (WSDL) file. This task describes the steps when using the top-down development approach.

When developing a JAX-RPC web service starting from an existing WSDL file, create the JavaBeans or enterprise bean and artifacts that enable the bean as web services and assemble all artifacts that are required for the web service, and deploy the application onto the application server.

Considerations when using JavaBeans

JavaBeans exposed as JAX-RPC web services are supported only over an HTTP transport.

Considerations when using enterprise beans
  • The enterprise bean must be a stateless session bean.
  • Enterprise beans that are exposed as JAX-RPC web services must be packaged in EJB 2.1 or in EJB 3.0 or higher modules.
  • For JAX-RPC web services using EJB 2.1 style endpoints, the Web service method parameters must be one of the supported JAX-RPC types. These requirements are documented in the JAX-RPC specification.
  • JAX-RPC web services using enterprise beans are supported over an HTTP or Java Message Service (JMS) transport.
Best practice Best practice: It is a best practice to use EJB 2.1 style enterprise beans with JAX-RPC applications. bprac

Procedure

  1. Set up a development environment for web services. You do not have to set up a development environment if you are using Rational® Application Developer.
  2. Develop the Java artifacts from a WSDL file. You need to create the deployment descriptor templates and bindings that are configured to map the service implementation to the JavaBeans or enterprise beans implementation.
  3. Complete the implementation of your web service application.
  4. Configure the webservices.xml deployment descriptor. For JAX-RPC web services, configure the webservices.xml deployment descriptor so that the application server can process the incoming web services requests.
  5. Configure the ibm-webservices-bnd.xmi deployment descriptor. Configure the ibm-webservices-bnd.xml deployment descriptor so that the application server can process the incoming web services requests.
  6. Assemble the artifacts for your web service.

    Use assembly tools provided with the application server to assemble your Java-based web services modules.

    If you have assembled an Enterprise Archive (EAR) file that contains enterprise beans modules that contain Web services, use the endptEnabler command-line tool or an assembly tool before deployment to produce a web services endpoint WAR file. This tool is also used to specify whether the web services are exposed using SOAP over Java Message Service (JMS) or SOAP over HTTP.

  7. Deploy the EAR file into the application server. You can now deploy the EAR file that has been configured and enabled for JAX-RPC web services onto the application server.

Results

You have developed a JAX-RPC web service application by starting with an existing WSDL file.

What to do next

After you deploy the EAR file, test the web service to make sure that it works with the application server.




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 4:16:02 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=matt&product=was-base-dist&topic=twbs_devwbsjaxrpcwsdl
File name: twbs_devwbsjaxrpcwsdl.html