Jersey 1.1.1-ea is released

We have just released version 1.1.1-ea of Jersey, the open source, production quality, reference implementation of the draft JAX-RS 1.1 API. The JAX-RS 1.0 specification and the 1.1 change log is available at the JCP web site and also available in non-normative HTML here.

It will be available soon from the GlassFish v2 and v3 update centers, and will be shipped with the latest GlassFish v3 builds.

To get started with Jersey read the getting started document. For an overview of JAX-RS features read the Jersey user guide. To understand more about what Jersey depends on read the dependencies document.

Between releases there has been some very interesting developments with a "sister" projected called Atmosphere. If you are interested in portable Comet support and how to avail of high-level ease of use support with Jersey check out JFA's latest blog entries.

This release took a little longer than expected with holidays post JavaOne, alignment with a version of JAXB for JSON namespace related features, a last minute XML-related security fix, and being hindered by the infrastructure:

  • Jakub has implemented the eagerly anticipated JSON namespace support for "mapped" (the default) and the "natural" conventions. In addition we have re-factored the JSONJAXBContext such that developers can use it to marshal and unmarshal JSON with JSONMarshaller and JSONUnmarshaller respectively.
  • Paul Bryan and Hubert Le Van Gong have added OAuth which comprises Jersey client and server support that leverages an OAuth signature library. The modules are currently located here, but for 1.1.2-ea-SNAPSHOT and future releases they are located here.
  • James Strachen has integrated support for lift templates with Jersey's MVC framework. The module is located here. To see Jersey, Scala and lift in action check out the RestMQ project.

See change log here.

The next release, 1.1.2-ea or 1.1.2, is tentatively scheduled for late August 2009 and is dependent on alignment with other EE 6 technologies such as Servlet 3.0 and JSR 299/330. In addition we plan to implement full OSGi support thanks to the help and guidance of Richard Wallace.

For feedback send email to: (archived here)

or log a bugs/features here.


Congrats on the release.

Posted by Daniel Shaw on July 15, 2009 at 11:19 AM CEST #

Please, pretty please, with sugar on top, move all these projects to Google Code, which also features release/download management, issue tracking, wiki, and soon Mercurial support. I get that some Sun middle manager has to somehow justify his position and so has created Kenai, but I'd rather if the people building the actual stuff that customers use didn't have to jump through useless hoops for his sake.

Posted by Mikael Gueck on July 16, 2009 at 09:05 AM CEST #

Hi Mikeal,

I am not happy with the current state of affairs: the project hosted at which is continually plagued by performance issues.

Moving to either Kenai or Google Code would be a big improvement over that of, regardless of the relative technical merits of Kenai and Google Code.

Unfortunately for the moment the project has to stay where it is. I have tried to reduce dependencies on by archiving email at nabble/MarkMail and SVN history available via FishEye.


Posted by Paul Sandoz on July 16, 2009 at 09:25 AM CEST #

Would you have anything against someone mirroring the sources for some of these projects on bitbucket etc incrementally?

It might be worth the one-time shot to get rid of the headaches.

What about the web pages hosted on, is there a repository for those as well, that one could just download automatically?

Posted by Mikael Gueck on July 16, 2009 at 10:59 AM CEST #

I imported the Jersey trunk into bitbucket. Glassfish v3 coming as we speak.

Posted by Mikael Gueck on July 16, 2009 at 06:37 PM CEST #

Hi Mikeal,

I have no objection to mirroring as long as the source does not get out of sync i.e. there has to be a canonical source tree still at

A number of people have mirrored/copied Jersey source onto github to do their own experimental modifications, but i think you are the first to create an actual mirror. Do you have the link at bitbucket?

How is the source synced up, does it have to be done manually?


Posted by Paul Sandoz on July 17, 2009 at 02:23 AM CEST #

Hi, I was really excited to learn RESTful and especially playing with Jersey. Definitively, this has changed my point of view on how to design web application over HTTP. But this was true until I discovered that it was impossible to manage the verb PUT and DELETE with HTML. And finally definitively disapointed when this was confirmed to me: Why REST Failed. (

So, now, why Jersey ? Why the JSR 311 if nothing is waiting for it? Show stopper...

Posted by exxos on July 18, 2009 at 03:35 PM CEST #

Hi Exxos,

Despair ye not. Elliot's attention grabbing headline is worthy of a tabloid newspaper :-) please do not take it so literally.

Bill's comment is most appropriate:

REST is a style for building scalable distributed systems. That style has been successfully applied to the architecture of the Web.

Jersey/JAX-RS is a Java-based framework helping build RESTful systems using the Web architecture (it is not restricted to utilizing HTML).

The fact that one component of the Web architecture, HTML forms (version < 5) , does not utilize PUT/DELETE, does not mean failure. Many good systems have been built that utilize just GET/POST (with forms). Could such systems have been richer if HTML forms utilized PUT/DELETE? yes they could. But it in no way invalidates the REST style and its benefits.

See HTML 5:


Posted by Paul Sandoz on July 20, 2009 at 04:44 AM CEST #

[Trackback] Atmosphere 0.3 released with support for Scala, Clustering, Injections, Grails Support, Cometd/Bayeux Protocol, many performance improvements, and many new extension points!!

Posted by Jean-Francois Arcand's Blog on July 23, 2009 at 09:31 PM CEST #

Post a Comment:
  • HTML Syntax: NOT allowed



« June 2016