Jersey 1.0 is released
By sandoz on Oct 13, 2008
We have just released version 1.0 of Jersey, the open source, production quality, reference implementation of the JAX-RS 1.0 API. The JAX-RS specification is available at the JCP web site and also available in non-normative HTML here.
To get started with Jersey read the getting started document. For an overview of JAX-RS features visit the Jersey wiki and read the overview document. To understand more about what Jersey depends on read the dependencies document. For details of the Jersey API go to here.
Jersey 1.0 is released to the Java.Net maven repository. Jars, source, JavaDoc and samples are all available from the following base URI:
All the samples can be obtained individually or as one zip file.
Jersey will be available soon from the Glassfish v2 and v3 update centers. And will be available in the Netbeans 6.5 release.
I decided to forgo a cycling themed picture this time and instead present a Castell. To quote Eduardo: "Many people need to do their tasks very well to build such a big castell". While the JAX-RS and Jersey castells may not require as many people as Glassfish i think the analogy still applies. Perhaps one could view Glassfish as an Escher like castell where each component is a castell itself? in any case i digress!
I would like to thank everyone that has contributed to the JAX-RS API and/or Jersey, whether it be the expert group members, comments on JAX-RS from external individuals (emails and blogs) and the many developers living on the edge trying out the Jersey early access releases, providing feedback and contributing code.
We have a better API because of the JCP process. With at least five different implementations of JAX-RS in development, four of them open source as of writing, the API was tested early and often.
We have a better reference implementation because we are open source, released early and often, and are responsive to the community.
What's next? In terms of JAX-RS the expert group will be starting a maintenance release to align with EE 6. In terms of Jersey here are some current aspects off the top of my head:
- improve the boundaries between Jersey modules (for OSGi) and further modularize, this will require name changes to some API packages;
- better MIME multipart support;
- investigate further comet/AJAX integraton; and
- improve the integration with IoC frameworks. It is hard to be abstract from any IoC framework.
there is much more and i plan to create a more complete set of short and long term tasks in the next couple of weeks. If you have ideas send email to:
or log a feature here.