Jersey 1.1.4 is released

We have just released version 1.1.4 of Jersey, the open source, production quality, reference implementation of JAX-RS. 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, is included in the latest GlassFish v3 builds and, assuming there are no show stoppers, this version will be included in the final GlassFish v3 release scheduled for December 10th.

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

This release integrates with other Java EE 6 technologies such as Servlet 3.0, EJB 3.1, managed beans and JCDI 1.0 and contains many bug fixes. See change log here.

The next release, 1.1.5, is tentatively scheduled for December or January. Hopefully this time we can fully resolve the OSGi'ification of Jersey that we have been promising for a while. In addition, now that the Java EE 6 features are done, we hope to resume some experimentation and new features and ensure we have good integration with Atmosphere.

For feedback send email to:

users@jersey.dev.java.net (archived here)

or log a bugs/features here.
Comments:

Congratulation!

Posted by beanor on November 12, 2009 at 08:12 PM CET #

What is the status of testing/versions for use of Jersey on Google App Engine? I've tried the 1.1.4 version, which attempts to use a non-whitelisted class javax.naming.InitialContext, which was mentioned on other blogs earlier this year. Their patched jar versions do not seem to fully work.

Ideally, I would like to start Jersey on GAE without any default providers. So that custom ones for JSON (Google GSON) and templating (Google Closure Templates) can be used (and no XML provider needed, so no JAXB issues on GAE).

Posted by Andy on November 20, 2009 at 05:47 AM CET #

Hi Andy,

There is an open issue that supplies some workarounds:

https://jersey.dev.java.net/issues/show_bug.cgi?id=379

We need to refactor the code that uses javax.naming to a separate jar (specifically this is for EE-related functionality it i think it does make sense in a separate jar).

Jersey does not have a static dependency on JAXB so if it is not in the classpath then it will not be used (there may be some errors logged that the JAXB components cannot be instantiated but it will not affect the running of Jersey). It might be possible to supply a stripped down version of Jersey core.

Note that if the application supplied providers then they can override the default ones.

Posted by Paul Sandoz on November 20, 2009 at 06:48 AM CET #

Yes I'd like to run Jersey on GAE too and also I don't need JAXB support now.

Thanks.

Posted by Iqbal Yusuf on November 25, 2009 at 11:37 AM CET #

Hi Iqbal, Andy,

I will take a look at this next week to see what we can do to refactor certain functionality.

First step is i need to get a GAE account!

Paul.

Posted by Paul Sandoz on November 25, 2009 at 01:10 PM CET #

Post a Comment:
  • HTML Syntax: NOT allowed
About

sandoz

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today