Monthly Archives: March 2012

Jersey 2.0-m02 has been released

After the first milestone release of Jersey 2.0 we continue running our development sprints. A few weeks passed, another sprint is over and we are happy to announce that a new milestone release of Jersey 2.0 is out.

The main theme for the Jersey 2.0-m02 sprint was to bring in the JAX-RS 2.0 asynchronous server-side support. The list of all the resolved feature requests, tasks and issues in this milestone can be browsed in our Jersey Jira. In summary, the new milestone adds

  • JAX-RS 2.0 server-side asynchronous processing support
  • JAX-RS 2.0 server-side content negotiation support
  • Integration with Java SE HTTP server as a Jersey 2.0 container
  • Improved JAX-RS parameter injection
  • Sub-resource locator processing support
  • Client-side JAX-RS Feature for JSON providers
  • Several bug fixes

For a complete overview of the new Jersey API, please have a look at the Jersey 2.0-m02 API documentation. Note that this is an early development preview release and the parts of the API are moving frequently so you can still expect significant changes in the API. You may want to bookmark the Jersey 2.0 snapshot API documentation link instead to make sure you look at the latest version of the API. Also feel free to browse Jersey 2 source code and check out the new examples that leverage JAX-RS 2.0 Client API as well as Jersey 2 server-side programmatic API.

The second early draft of JAX-RS 2.0 specification is available at the JCP web site. The latest version of JAX-RS 2.0 API documentation is also available for browsing here. This link and more information about the JAX-RS project can be found on the JAX-RS project web site.

Current milestone release supports Java SE HTTP Server, Grizzly 2 HTTP container as well as basic Servlet-based deployments on the server side and provides HTTPURLConnection-based client API implementation. All the 2.0-m02 milestone binaries including the source & apidocs jars 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.

To run Jersey 2 you’ll need the core artifacts:


Additionally, you’ll need a Jersey container implementation, e.g. Jersey Grizzly2 HTTP container:


Have fun looking around, running examples, playing with Jersey 2. To provide feedback send us an email to our users mailing list (archived here)

or log discovered bugs & new feature requests in Jersey Jira issue tracker.