...
| Info | ||
|---|---|---|
| ||
JAX-RPC didn't used JAXB because the first version of JAX-RPC is was completed much before JAXB. So, instead of waiting for JAXB to complete JAX-RPC writers developed their own custom mapping. |
...
As per JAX-RPC a Service Endpoint Interface must extend Remote. JAX-WS removes this condition and you can pretty much make a POJO class a Web Service by just adding the @WebService annotation at the top of the class.
...
- Annotations - JAX-WS requires that all SEIs include the
@WebServiceannotation - java.rmi.Remote - The JAX-RPC SEI extends the java.rmi.Remote interface. JAX-WS no longer requires this.
...
- The creation of ServiceFactory instance is no longer required for creating the Service
- Service maps to javax.xml.rpc.Service in JAX-RPC and to javax.xml.ws.Service in JAX-WS.
RESTful services
JAX-WS introduced introduces RESTful Web Services as successor for SOAP based Web Service. RESTful services have already got quite support from many vendors like Google AdSense, Yahoo API's, Amazon and so on.
The important things that are introduced in JAX-WS to support RESTful services are:
...
JAXWS 2.0 brings in support for optimized transmission of binary data as specified by MTOM (SOAP Message Transmission Optimization Mechanism) and SAAJ (SOAP with Attachments API for Java).
MTOM allows optimized transmission of binary data - any xs:base64Binary or xs:hexBinary schema type can be send sent as attachment following rules defined by MTOM specification.
...