Monthly Archives: June 2012

Jersey 2.0-m05 has been released

Yesterday, the Jersey team has released Jersey 2.0-m05. The theme of the scrum sprint was to integrate Jersey 2.0 into the development trunk of GlassFish and switch core Jersey code to the latest JAX-RS API which contains significant changes in message filtering API. I am happy to report that we succeeded in delivering both main goals.

The new Jersey 2.0 code has replaced the old Jersey 1.x in GlassFish development branch, thanks to Jakub (currently the integrated Jersey version is 2.0-m04-2 and we are working on integrating the recently released 2.0-m05 momentarily). Since the Jersey 2.0 is based on a completely new codebase and internal APIs, the switch of Jersey versions in GlassFish was not an easy task at all.

The other goal to switch to the latest JAX-RS API 2.0-m09 which contains significant API changes compared to the formerly used 2.0-m05 milestone version was similarly demanding, with great support from all Jersey team members, including our manager (yes, our manager CAN code! :-)), we made it and the new core infrastructure design, robustness and stability was further improved.

If you are interested in more details, the list of all the resolved feature requests, tasks and issues in the Jersey 2.0-m05 sprint can be browsed in our Jersey Jira.

For a complete overview of the updates in the Jersey API, please have a look at the Jersey 2.0-m05 API documentation. Note that we are still in the middle of a development cycle and Jersey 2.0-m05 is an early development preview release so you can still expect significant changes in the API since the parts of the API are moving every now and then. You may want to also bookmark the Jersey 2.0 snapshot API documentation link to if you want to see the latest development version of the API. Also feel free to browse Jersey 2 source code and check out the examples that leverage JAX-RS 2.0 Client API as well as Jersey 2 server-side programmatic API.

In this sprint we also continued work on an updated user guide that also contains an initial draft of a migration guide for your Jersey 1.x code. Again, as with API documentation, you may want to bookmark the Jersey 2.0 snapshot user guide to see the very latest updates to the guide.

The third 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.

Another important news from the last sprint is that Jersey is now available on github as a first-class citizen. So if you prefer accessing the code over github to accessing it over, check it out. As I said, Jersey is now finally a first-class github citizen, which means that we have also setup the necessary automatic build and verification infrastructure to be able to accept any github pull request from the community. (A funny thing – the first fork of the Jersey repository on github came from a RedHat guy :-P)

Jersey 2.0 provides support for Java SE HTTP Server, Grizzly 2 HTTP server, Servlet 2.5 or higher containers as well as OSGi containers on the server side and HTTPURLConnection-based or Grizzly asynchronous client transport connectors. To leverage JAX-RS/Jersey server-side async features in the servlet container, you need a container that supports Servlet 3.0 at least. Jersey supports asynchronous resource invocations on Grizzly 2 HTTP server too.

All the 2.0-m05 milestone binaries, including the source & apidocs jars, are available for download under the Jersey 2.0 maven root group identifier org.glassfish.jersey from the central maven repository as well as from 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:


Chances are you are using maven on your project. If you do, there is a very easy and convenient way to start playing with Jersey 2.0 by generating the skeleton application from one of the Jersey 2.0 maven archetypes that we provide. For instance, to create a Jersey 2.0 application using the Grizzly 2 HTTP server container, use

mvn archetype:generate -DarchetypeGroupId=org.glassfish.jersey.archetypes -DarchetypeArtifactId=jersey-quickstart-grizzly2 -DarchetypeVersion=2.0-m05

If you want to create a Servlet container deployable Jersey 2.0 web application instead, use

mvn archetype:generate -DarchetypeGroupId=org.glassfish.jersey.archetypes -DarchetypeArtifactId=jersey-quickstart-webapp -DarchetypeVersion=2.0-m05

Have fun looking around, running examples, testing new additions to the set of features and 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.