2.15
Release date: 14-Jan-2015
Highlights
Container agnostic CDI support
Before 2.15, CDI integration was supported primarily in Java EE containers with built-in CDI support. From version 2.15 onwards, it is possible to leverage CDI integration also outside of Java EE environment. A new example, helloworld-weld, has been introduced to demonstrate the new feature using Grizzly HTTP server. Another example application, cdi-webapp, has been updated so that it enables Apache Tomcat Server deployment.
Breaking Changes
CDI support improvement caused breaking changes for those users directly referring to the following CDI supporting Jersey module in maven:
<dependency> <groupId>org.glassfish.jersey.containers.glassfish</groupId> <artifactId>jersey-gf-cdi</artifactId> <version>${pre-2.15-version}</version> </dependency>
The above dependency needs to be replaced with:
<dependency> <groupId>org.glassfish.jersey.ext.cdi</groupId> <artifactId>jersey-cdi1x</artifactId> <version>2.15</version> </dependency>
The following needs to be included in addition if you want to leverage CDI JTA support:
<dependency> <groupId>org.glassfish.jersey.ext.cdi</groupId> <artifactId>jersey-cdi1x-transaction</artifactId> <version>2.15</version> </dependency>
Bug
- [JERSEY-2558] - ChunkedOutput.close() broken since Jersey 2.8
- [JERSEY-2622] - NPE at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:300)
- [JERSEY-2651] - JAX-RS filters are not registered if they are Spring managed components
- [JERSEY-2721] - Proxy client fails to send an entity if it has any annotation
- [JERSEY-2739] - "NameBinding" results in a deployment failure
- [JERSEY-2750] - @RolesAllowed does not work in JettyHttpContainer
Improvement
- [JERSEY-2650] - Unnecessary copy of el-api is deployed to WEB-INF due to compilation dependency in jersey-declarative-linking extension
Task
- [JERSEY-2017] - CDI integration should be provided as AS agnostic, CDI 1.0 and CDI 1.1 modules in Jersey