JAX-RPC vs JAX-WS

Comparison between JAX-RPC and JAX-WS
Functionlity	JAX-RPC	JAX-WS
SOAP 1.2	JAX-RPC and JAX-WS support SOAP 1.1	JAX-WS also supports SOAP 1.2.
HTTP Binding	JAX-RPC ignored the HTTP binding.	The WSDL 1.1 specification defined an HTTP binding, which is a means by which you can send XML messages over HTTP without SOAP. JAX-WS adds support for it.
WS-I's Basic Profiles	JAX-RPC supports WS-I's Basic Profile (BP) version 1.0.	JAX-WS supports BP 1.1. (WS-I is the web services interoperability organization.)
New Java features	JAX-RPC maps to Java 1.4.	JAX-WS maps to Java 5.0. JAX-WS relies on many of the features new in Java 5.0.
Annotation Supports	JAX-RPC does not support annotation.	JAX-WS features a collection of annotations to be used to define Web Service endpoints and Web Service clients.This simplifies development a lot, since the developer adds annotations to the implementation classes instead of writing a lot of descriptors.
The data mapping model	JAX-RPC has its own data mapping model, which covers about 90% of all schema types. Those that it does not cover are mapped to javax.xml.soap.SOAPElement.	JAX-WS's data mapping model is JAXB. JAXB promises mappings for all XML schemas
The interface mapping model	JAX-WS's basic interface mapping model is not extensively different from JAX-RPC's	JAX-WS's model introduces asynchronous functionality.
The dynamic programming model	JAX-RPC does not have dynamic server model.	It introduces message-oriented and dynamic asynchronous functionalities. JAX-WS also adds a dynamic server model
MTOM (Message Transmission Optimization Mechanism)	JAX-RPC does not support MTOM	JAX-WS, via JAXB, adds support for MTOM. MTOM can send and receive binary data optimally without incurring the cost of data encoding to ensure the data is included in the XML document.
The handler model	JAX-RPC handlers rely on SAAJ 1.2.	JAX-WS handlers rely on the new SAAJ 1.3 specification.