Major new features for Jersey

Jersey 2.0 Milestone 2 shores up

Chris Mayer

More work has been done towards the reference implementation for JAX-RS 2.0, so we may be close to a fully equipped Java API for RESTful HTTP services

The second milestone for the reference implementation of JAX-RS 2.0 has arrived. Jersey 2.0 M2 continues upon the good work of the first with the addition of some nifty new features.

Marek Potociar revealed the news on his blog telling us of the team’s ‘production sprints’ to get this second release done, with the main goal being to bring in the JAX-RS 2.0 asynchronous server-side support. This is a huge part of the project which is now almost fully realised.

Other important features added include JAX-RS 2.0 server-side content negotiation support, integration with Java SE HTTP server as a Jersey 2.0 container and improved JAX-RS parameter injection. There’s also the inclusion of sub-resource locator processing support and a new client-side JAX-RS feature for JSON providers.

As Potociar states, this is still work in progress. After all, it’s an ‘early development preview release and the parts of the API are moving frequently’ so changes are to be expected as time goes by. 

REST endpoints can be published on Java SE HTTP Server, Grizzly 2 HTTP container, and other basic Servlet-based deployments. It also provides HTTPURLConnection-based client API implementation. All relevant binaries are available for download under a new Jersey Maven root group identifier org.glassfish.jersey from the central Maven repository as well as in the Maven repository.

Jersey is the reference implementation of JSR 339: “JAX-RS 2.0: The Java API for RESTful Web Services“, which is part of the Java EE-7 specification that is currently being completed. You can see a second Early Draft of JAX-RS 2.0, on the JCP website. 

If you’re interested in JSR 339 you best check out the latest work behind Jersey.

Inline Feedbacks
View all comments