For an overview of changes, bug fixes, new features and 7 merged GitHub pull requests, please consult Jersey 2.16 Release Notes.
JAX-B providers separated from the core
From version 2.16 onwards, all JAX-B providers are being bundled in a separate module.
The main motivation behind that is t allow using Jersey Client on Android. Current status of Android support has been described by Jakub Podlešák in his Jersey 2.x Client on Android blog post.
Performance gain when using Sub-Resource Locators
We improved the performance for using sub-resource locators in an Jersey application. The performance gains are available for cases when the sub-resource locator method returns either a resource class (return value is e.g. Class<?> or Class<MySubResource>) or a (non-proxied) resource instance (when return value is an instance of MySubResource class).
This is described by Michal Gajdoš in more detail in his Performance Improvements of Sub-Resource Locators in Jersey blog post.
Another blog post about is again by Jakub about general Jersey 2 performance improvements.
More unified connector configuration options
Jetty connector and Apache connector have been previously using their own custom properties to set SSL context on a connector. These properties have been deprecated and the code has been updated to read the SSL context information from the JAX-RS client configuration. This means that all Jersey connectors now properly accept SSL configuration as configured via standard JAX-RS ClientBuilder methods.
Previously, all Jersey connectors have been using their own default chunk size when HTTP chunked coding was used. Since Jersey 2.16, there is a new default chunk size value used by all connectors, if a custom chunk size is not set. The new default value is stored under ClientProperties.DEFAULT_CHUNK_SIZE client property.
To download Jersey 2.16, please check our download page.
You can also check out the refreshed Jersey 2.16 documentation:
- API: https://jersey.java.net/apidocs/2.16/jersey/
- User Guide: https://jersey.java.net/documentation/2.16/
Other blog posts
- Container Agnostic CDI Support In Jersey by Jakub - Jersey 2.5 introduced Weld SE support, so that people could take advantage of CDI features also when running in Java SE environment.
- Upload file to MongoDB using Jersey 2 by Adam Lindenthal - Using GridFS to store files accepted by RESTful API.
- Jersey’s Entity Filtering meets Jackson by Michal - Entity Filtering in Jersey introduces a convenient facility for reducing the amount of JSON data exchanged over the wire between client and server without a need to create specialized data view components. Since Jersey 2.6 Entity Filtering feature is implemented with Moxy and as well as Jackson now.
- Intercepting Jersey resource method calls by Michal - In Jersey 2 it is possible to intercept resource method calls outside CDI but via HK2.
or log bugs/features here.