The administration function of the product is enhanced to support installing and deploying Java Application Programming Interface (API) for XML Web Services (JAX-WS) applications like any other WebSphere Application Server applications.
A JAX-WS application is packaged as a Web archive (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. You can deploy your 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 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:
When the service is a JavaBeans-based or Web module-based service,
the following files and deployment descriptors are required:
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.
|
No deployment descriptors are required for a JAX-WS Web service. |