Artifacts used to develop Web services

With development artifacts we can develop an enterprise bean or a Java Beansmodule into a Web service. This page describes artifacts used to develop Web services that are based on the Web Services for Java EE specification.

To create a Web service from an enterprise bean or from a Java Beans module, the following files are added to the respective JAR file or WAR modules at assembly time:

• WSDL Extensible Markup Language (XML) file

  The WSDL XML file describes the Web service that is implemented.

• Service Endpoint Interface

  A Service Endpoint Interface is the Java interface corresponding to the Web service port type implemented. The Service Endpoint Interface is defined by the JAX-WS or JAX-RPC Web services run time that we are using.

• webservices.xml

  The webservices.xml file contains the Java EE deployment descriptor of the Web service specifying how the Web service is implemented. The webservices.xml file is defined in the Web Services for Java EE specification.

  For JAX-WS Web services, the use of the webservices.xml deployment descriptor is optional because we can use annotations to specify all of the information contained within the deployment descriptor file. Use the deployment descriptor file to augment or override existing JAX-WS annotations. Any information that you define in the webservices.xml deployment descriptor overrides any corresponding information specified by annotations.

  For JAX-RPC applications, deployment descriptors are required to specify how the Web service is implemented.

• ibm-webservices-bnd.xmi (JAX-RPC applications only)

  This file contains WebSphere product-specific deployment information and is defined in ibm-webservices-bnd.xmi assembly properties.

• Java API for XML-based remote procedure call (JAX-RPC) mapping file

  The JAX-RPC mapping deployment descriptor specifies how Java elements are mapped to and from WSDL file elements.

The following files are added to an application client, enterprise beans or Web module to permit a Web Services for Java EE client access to Web services:

• WSDL file

  The WSDL file is provided by the Web service implementer.

• Java interfaces for the Web service

  The Java interfaces are generated from the WSDL file as specified by the JAX-WS or JAX-RPC specification. These bindings are the Service Endpoint Interface based on the WSDL port type, or the service interface, which is based on the WSDL service.

• ibm-webservicesclient-bnd.xmi (JAX-RPC applications only)

  This file contains WebSphere product-specific deployment information, such as security information for JAX-RPC applications. For JAX-WS applications, deployment descriptors are not supported and have been replaced by the use of annotations.

• Other JAX-RPC binding files

  Additional JAX-RPC binding files that support the client application in mapping SOAP to the Java language are generated from WSDL by the WSDL2Java command tool.

---

 

Related tasks

Task overview: Implement Web services applications
Implement Web services applications with JAX-WS
Implement Web services applications from existing WSDL files with JAX-WS
Implement Web services applications with JAX-RPC
Implement Web services applications from existing WSDL files with JAX-RPC

 

Related

JAX-RPC Web services enabled module - deployment descriptor settings (ibm-webservices-bnd.xmi file)
WSDL2Java command for JAX-RPC applications
Web services specifications and APIs