Here are some links to documentation and examples to help you evaluate what each client can offer in descending order of my personal recommendations, from the best to general and some links to other comparisons that I found.
RESTEasy Feature List
- Portable for Tomcat and many other server applications
- Implemented server implementation for testing JUnit
- Extended customer infrastructure
- Caching Features: Browser client cache. Supports HTTP 1.1 caching semantics, including cache reevaluation
- Server cache in memory. Local response cache. Automatic processing of ETag generation and re-checking the cache.
- A rich set of suppliers for: XML, JSON, YAML, Fastinfoset, Multipart, XOP, Atom, etc.
- JAXB, combining XML, JSON, Jackson, Fastinfoset, and Atom, as well as wrappers for maps, arrays, lists, and sets of JAXB objects.
- GZIP Content Encoding
- HTTP Asynchronous Paragraphs (Comet) for JBoss Web, Tomcat 6, and Servlet 3.0
- Asynchronous service work.
- A rich interceptor model.
- OAuth2 and Distributed SSO with JBoss AS7
- Digital Signature and Encryption Support with S / MIME and DOSETA
- EJB, Seam, Guice, Spring, and Spring MVC Integration
- There was no RESTEasy Spring Boot startter, so the PayPal team decided to create a RESTEasy Spring Boot Starter and share it with the community.
RESTEasy examples see also Three forms of the RESTEasy client
- The Jersey RESTful web services framework is open source, product quality, a Java RESTful web services framework that provides JAX-RS API support and serves as a JAX-RS implementation (JSR 311 and JSR 339). The Jersey snippet is bigger than the JAX-RS Reference implementation. Jersey provides its own API, which extends the JAX-RS toolkit with additional features and utilities to further simplify RESTful service and customer development. Jersey also provides numerous broad-based SPIs so that developers can extend the Jersey to best suit their needs.
The objectives of the Jersey project can be summarized in the following paragraphs:
- Track the JAX-RS API and provide regular product quality releases. Reference Implementations that ship with GlassFish;
- Provide APIs to expand the Jersey network and create a community of users and developers; and - simplify the creation of RESTful web services using Java and the Java virtual machine.
There are several Jersey-based connectors, see chapter 5. Client API 5.5. Client transport connectors, while Grizzly looks the most advanced, especially because it uses the NIO infrastructure to help developers take advantage of the Java ™ API NIO see java.net versus java.nio , it was used with the AsyncHttpClient progect , what you need.
By default, the transport layer in Jersey is provided by HttpUrlConnection. This transport is implemented in Jersey through the HttpUrlConnectorProvider, which implements a Jersey-specific SPI. You can implement and / or register your own connector instance to implement the Jersey client, which will replace the default transport layer based on the HttpUrlConnection. Jersey provides several alternatives for ready-to-use client transportation connections.
Table 5.1. Jersey Connections List Jersey Transport Structure Connector Implementation Maven Dependency
Jersey vs RESTEasy: JAX-RS implementation comparison
- Sprint RestTemplate or for asynchronous calls to the AsyncRestTemplate shutdown API see Spring 4 AsyncRestTemplate + ListenableFuture Example is the standard Spring Restarter api boot starter. There was no RESTEasy Spring Boot startter until the PayPal team decided to create a RESTEasy Spring Boot Starter and share it with the community.
Tomer bar-shlomo
source share