JAX-WS application deployment model

Network Deployment (Distributed operating systems), v8.0 > Develop and deploying applications > Develop web services > Deploy web services > Deploy web services applications onto application servers

JAX-WS application deployment model

The administration function of the product is enhanced to support installing and deploying Java API for XML Web Services (JAX-WS) applications like any other WAS applications.
A JAX-WS application is packaged as a WAR file or a WAR module within an Enterprise Archive (EAR) file. The JAX-WS application deployment model is similar to the Java API for XML Remote Protocol Call (JAX-RPC) web services application model. The main difference between them is that JAX-RPC web services application requires you to add additional bindings and deployment descriptors for application deployment. A JAX-WS application does not require additional bindings and deployment descriptors for deployment. We can deploy your JAX-WS applications as you would deploy any other WAS application.
JAX-WS web services is a rewrite of JAX-RPC web services. The table compares the web services stack for both JAX-WS and JAX-RPC web services.

JAX-RPC web services JAX-WS web services
Bindings are proprietary Bindings are based on the open source Java API for XML Bindings (JAXB)
Parsing is proprietary Parsing is based on the open source Java Specification Request (JSR) 173
No Java annotations support Support for Java annotations such as @WebService, @WebMethod, @WebParam, @WebResult, and @SOAPBinding
During deployment, some deployment descriptor files are created in a JAX-RPC based service and client.
The following files are created on the services side, when it is an EJB based web service and EJB based module:

webservices.xml
<name_of_service>_mapping.xml
ibm-webservices-bnd.xmi
ibm-webservices-ext.xmi

When the service is a JavaBeans-based or web module-based service, the following files and deployment descriptors are required:

webservices.xml
<name_of_service>_mapping.xml
In the web.xml file, there is no additional content
ibm-webservices-bnd.xmi
ibm-webservices-ext.xmi

The web.xml exists in both EJB and JavaBeans based services. However, there is no additional content added to the file during deployment of a Web service application or module.
For JAX-WS web services, the use of the webservices.xml deployment descriptor is optional because you can use annotations to specify all of the information that is contained within the deployment descriptor file. We can 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 transitioning users: Starting with WAS v7.0 and later, Java EE 5 application modules (web application modules version 2.5 or above, or EJB modules version 3.0 or above) are scanned for annotations to identify JAX-WS services and clients. However, pre-Java EE 5 application modules (web application modules version 2.4 or before, or EJB modules version 2.1 or before) are not scanned for JAX-WS annotations, by default, for performance considerations. In the v6.1 Feature Pack for Web Services, the default behavior is to scan pre-Java EE 5 web application modules to identify JAX-WS services and to scan pre-Java EE 5 web application modules and EJB modules for service clients during application installation. Because the default behavior for WAS Version 7.0 and later is to not scan pre-Java EE 5 modules for annotations during application installation or server startup, to preserve backward compatability with the feature pack from previous releases, configure either the UseWSFEP61ScanPolicy property in the META-INF/MANIFEST.MF of a WAR file or EJB module or define the JVM custom property, com.ibm.websphere.webservices.UseWSFEP61ScanPolicy, on servers to request scanning during application installation and server startup.
To learn more about annotations scanning, see the JAX-WS annotations information.trns
JAX-WS application packaging
Develop JAX-RPC web services deployment descriptor templates for a JavaBeans implementation
Web services
Develop a webservices.xml deployment descriptor for JAX-WS applications
Deploy and administering enterprise applications
Deploy web services applications onto application servers

Related

Artifacts used to develop web services
JAX-WS annotations
Web services specifications and APIs

+
Search Tips | Advanced Search

JAX-RPC web services	JAX-WS web services
Bindings are proprietary	Bindings are based on the open source Java API for XML Bindings (JAXB)
Parsing is proprietary	Parsing is based on the open source Java Specification Request (JSR) 173
No Java annotations support	Support for Java annotations such as @WebService, @WebMethod, @WebParam, @WebResult, and @SOAPBinding
During deployment, some deployment descriptor files are created in a JAX-RPC based service and client. The following files are created on the services side, when it is an EJB based web service and EJB based module: webservices.xml <name_of_service>_mapping.xml ibm-webservices-bnd.xmi ibm-webservices-ext.xmi When the service is a JavaBeans-based or web module-based service, the following files and deployment descriptors are required: webservices.xml <name_of_service>_mapping.xml In the web.xml file, there is no additional content ibm-webservices-bnd.xmi ibm-webservices-ext.xmi The web.xml exists in both EJB and JavaBeans based services. However, there is no additional content added to the file during deployment of a Web service application or module.	For JAX-WS web services, the use of the webservices.xml deployment descriptor is optional because you can use annotations to specify all of the information that is contained within the deployment descriptor file. We can 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.