jersy vs apache cxf

Well jersy is a simple framework for REST full web services. Usage of it is pretty straight forward. Apache cxf is better if you need to work with SOAP web services. It all depends on what protocol you like to use. if REST then jersy works well while for SOAP apache cxf does the job.

Another thing to notice is that SOAP uses WSDL and the equivanlent of it in REST world is WADL. But still WADL is not standardized.

http://en.wikipedia.org/wiki/Web_Application_Description_Language.

For more info read the following article.

http://stackoverflow.com/questions/2704700/java-rest-implementation-jersey-vs-cxf

A simple resutfull implementation with jersy is described in the below article.

http://www.vogella.com/tutorials/REST/article.html

Apache axis 2 or Apache cxf?

Read the following post found on stackoverflow.
http://stackoverflow.com/questions/14933374/diffrence-between-axis2-webservice-and-cxf-web-service

Want to create a simple RESTFULL web service in java?

You can easily implement a RESTFULL web service using jersy libraries. The codes need to implement it a simple and clean. Visit the below link. You will see how.

http://www.javacodegeeks.com/2013/11/restful-web-services-with-java.html

xml-rpc vs soap vs rest pros and cons

Ok well as in some of the posts I've done, I'm going to redirect you to a url that has described this topic in very nice simple but in a detail manner. Hats off to the person who wrote this article in a such cool yet very analytic manner. So checkout the below link.

http://maxivak.com/rest-vs-xml-rpc-vs-soap/

RPC vs Document based webservices in jax-ws

Yeah I know the SOAP based web services are no longer widely used since REST based web services have decreased the usage of SOAP based services. Today how ever I wanted to talk about the differences in two types of SOAP based web services (RPC and SOAP).

RPC based web service with jax-ws

This type of webservices does marshalling and unmarshalling in the SOAP engine. Therefore if the message is large, then the conversion becomes a huge overhead. Hence implementing coarse grained funtionality becomes a problem. Also inter-operatability of this type is not that good plus the support for custom data types is very low since the restrictions on encoding styles. However on the other hand, the implementation of this type of a web service using jax-ws is very simple. And also is good for fine grained functionality. 

Document based web services are have the qualities exactly opposite to the above mentioned rpc based qualities. They are widely used where you need to transfer lots of data using large xml files. 

By comparison however the document based web services are used than rpc based services.