Comparison of JAX Rest Implementation

 In this Post we are going to compare diffrenet Rest implementation .

The parameters/ functional attributes which we  can be used to compare them  are

JAX-RS implementation parameters

• Embedded container support
• Client API framework
• Interceptor framework
• Data format support
• Component integration support
• Maturity of the product
• Server-side Integration Strategies
• Configurability
• Security
• Performance

CXF:
 CXF is a merger between XFire and Celtix (an Open Source ESB, sponsored by IONA and originally hosted at ObjectWeb).

Pros: Great to parse a WSDL and create Java POJOs to interact with, so CXF is pretty good for client-side WSDL service
s Jersey is mainly devoted to RESTful services and CXF deals mostly (all?) with SOAP
 CXF is  devoted to RESTful services and SOAP as well.
 deeper Inetgeration with spring.

 Cons:
 Inconsistencies in how I needed to handle SSL and HTTP Proxies

Restlet:
probably the first REST framework, which existed prior to JAX-RS.
Pros

 Restlet supports RESTful web services running as a standalone application, or inside a standard Servlet container. It's many extensions, and the ability to make your own, also enable it to integrate easily into an organization's existing software ecosystem.
 Less abstraction
An open, flexible, and effective development process; a solid community; and an emphasis on stability and strong support of current releases.
 Cons: When it comes to demarshalling the response into java object you have to do it manually.

 A Restlet application cannot only run inside a Servlet container, but can also be run as a standalone Java application using a single "org.restlet.jar" JAR.

Jersey :
- The JAX-RS Reference Implementation from Sun.

 Pros:
 In Netbeans the integration is full
Reference implementation of the JAX-RS API, which the upcoming Restlet 2.0 also implements.
Jersey is usually deployed within a servlet container but does support an embedded mode of operation within Java programs.
Component integration

Jersey currently provides extension-based support for two dependency injection frameworks: the Spring Framework and the Google Guice framework:

    Spring Framework. Spring support in Jersey requires a dependency on the jersey-spring module. Spring support is enabled by referencing the SpringServlet class in the web.xml file.
    Google Guice framework. Guice support is provided when referencing the Guice filter GuiceFilter and a Guice-specific ServletContextListener in the web.xml file.

 Cons:
 Jersey is mainly devoted to RESTful services and CXF deals mostly (all?) with SOAP
Issues with the Jersey/Spring integration, mainly with AOP.

NetKernel:
Pros:
NetKernel can be run as its own platform or it can be instantiated as a POJO run embedded in any Java program or container.
It is a REST software platform that is written in Java, runs on the Java VM and supports languages that compile to or run on the JVM (Scala, Ruby, Python, JavaScript, XQuery, XSLT, etc.).



Resteasy:
- JBoss's JAX-RS project.
Pros:
if component integration is of primary importance, the Restlet Framework or RESTEasy might be a good choice.
Being a JBoss-driven implementation, it's not surprising that RESTEasy supports close integration with JBoss Seam. However, it also supports integration with other popular frameworks and standards like Enterprise JavaBean (EJB) technology (a Java Platform, Enterprise Edition [Java EE] standard), Spring, and Google Guice.

Metro:
Oracle provides Metro for Rest Implementaion.However latest develeopment have been stopped for last three years.

AXIS2:

Pros:
  Axis2 is structured modularly, has many features and can be used as an application server for Web Services.
support of exchangeable binding frameworks, for example XMLBeans. Axis2 together with the XMLBeans framework is well suited for Web Services which are using very complex schema definitions.

Cons:
The disadvantages of Axis2 are its complexity as well as the insufficient JAX-WS support. Therefore anyone who wants to work with JAX-WS should choose Apache CXF or the reference implementation.