Jersey 2.0-m03 has been released

Again, a few weeks passed, another Jersey sprint is over and we are happy to announce that a new milestone release of Jersey 2.0 is out.

The list of all the resolved feature requests, tasks and issues in the Jersey 2.0-m03 sprint can be browsed in our Jersey Jira. In summary, the new milestone adds

  • JAX-RS 1.1 TCK compliance – an important milestone for the new redesigned codebase
  • JAX-RS 2.0 Reference Implementation (RI) bundle
  • Refactoring of the resource configuration API
  • Support for automatic HEAD & OPTIONS method generation
  • Jersey module OSGi-fication
  • Archetypes for Servlet and Grizzly-based applications
  • Security context injection (preliminary support)
  • Quite a lot of bug fixes

For a complete overview of the new Jersey API, please have a look at the Jersey 2.0-m03 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 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.

As in the previous milestone, the 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. Additionally, this milestone brings support for a couple OSGi features – HTTP Service and WAB – check out the OSGi related examples for more details. All the 2.0-m03 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 java.net maven repository.

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

org.glassfish.jersey.core:jersey-common
org.glassfish.jersey.core:jersey-server
org.glassfish.jersey.core:jersey-client

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

org.glassfish.jersey.containers:jersey-container-grizzly2-http

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

use...@jersey.java.net (archived here)

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

4 thoughts on “Jersey 2.0-m03 has been released

  1. Tomek Adamczewski

    Hi Marek,

    Have you tried to deploy Jersey2 webapp on any JEE 6 container? I’m playing with Glassfish for a while but can’t solve the classloader problems (as Glassfish loads Jersey1 implementation). Reversing classloader hierarchy doesn’t work for me so far. Any hints or examples?

    Regards,
    Tomek

  2. Marek Potociar Post author

    Good question. Currently we are running our tests on Grizzly, Jetty, Tomcat and Felix. The Glassfish poses a specific problem, since Jersey 1.x is part of the very core of the GF app server that uses old Jersey 1.x specific APIs and is thus not easy to replace. We are currently working on integrating new Jersey2 runtime into development builds of GlassFish 4. The work is in progress yet and we expect to be done with the initial integration work in a few weeks. Even after that, running Jersey2 on GF earlier than 4.0 will unfortunately not work – at least for now.

  3. Hugo

    Hi Marek, just a question with which version of Tomcat are you running it? and would it work on a Tomcat 5.5.1 ? <– i'm having trouble with the classloading on the 5.5.1

  4. Marek Potociar Post author

    We’re currently using Jetty to run our servlet-based tests. You should be however able to use Tomcat too – at least a version that supports Servlet 2.5, for async features a version supporting Servlet 3.0 would be required.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>