JAX-WS application deployment model

JAX-WS application deployment model

The administration function of the product is enhanced to support installing and deploying JAX-WS applications like any other WebSphere Application Server applications.
A JAX-WS application is packaged as a WAR file or a WAR module within an EAR file. The JAX-WS application deployment model is similar to the Java API for JAX-RPC web services application model. The main differences are 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 the JAX-WS applications as you would deploy any other WebSphere Application Server 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 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, using webservices.xml is optional. We can use annotations to specify all of the information contained within the deployment descriptor file. We can use the deployment descriptor file to augment or override existing JAX-WS annotations. Information defined in webservices.xml overrides any corresponding information specified by annotations.

Starting with WAS Version 7.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 Version 6.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 v7 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.

Related concepts

JAX-WS application packaging
Develop JAX-RPC web services deployment descriptor templates for a JavaBeans implementation
Web services

Related tasks
Develop a webservices.xml deployment descriptor for JAX-WS applications
Deploy
Artifacts used to develop web services
JAX-WS annotations
Web services specifications and APIs

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 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, using webservices.xml is optional. We can use annotations to specify all of the information contained within the deployment descriptor file. We can use the deployment descriptor file to augment or override existing JAX-WS annotations. Information defined in webservices.xml overrides any corresponding information specified by annotations.