Jersey 0.7 is released

Jersey

We have just released version 0.7 of Jersey (see the stable download directory). This aligns with the 0.7 release of the JAX-RS API and the March editors draft.

This version will be available soon from the Glassfish Update Centre.

Phew! this was a tough one. There were many additions and clarifications to the API. The email statistics for the 311 EG list looks like a climb profile (maybe up Alpe D'Huez like Lance if you squint your eyes).

So most of our time was spent on API aspects.

However, Jakub got some good feedback on the JSON support and fixed related bugs.

Martin Grotzke has been working on improving Spring, and in general IoC integration, support in a branch. The plan is to make this part of the 0.8 distribution, and hopefully we will manage to solve some difficult issues w.r.t. mixing IoC-based and Jersey-based components when injecting parameters of constructor/methods that Jersey is responsible for invoking.

I finally managed to play around with the latest JavaRebel and SDK and formalize the reloading of the Jersey runtime when resource classes are added, modified or removed. 

As a nice bonus Jean Francois kindly visited Grenoble for a day and we hashed out a Grizzly/Comet/Jersey prototype. I think we may have a very interesting and simple way of integrating Comet functionality with resource classes. Jean Francois has created a branch and we will work from that to progress such support. Unfortunately i did not have time to move to Grizzly 1.7.3 but i am very excited about prospects for 1.8.0 and an asynchronous client-side API based on Grizzly as i can make good use of that with the Jersey client-side API. 

Now it is time to prepare for JavaOne. Marc and I have a technical session on JAX-RS @ Tuesday 12:10. Jakub and I have a BOF on Jersey @ Tuesday 20:30. I should be around for the GF unconference on the Sunday before, and will be partially around for the CommunityOne event on the Monday before (Marc and I have to prepare for the session so we cannot attend for the whole day).

I am thinking of two possible dates for the 0.8 release, 20th June or the 25th of July. The reason being is the Jazoon conference is at the end of June, we need to relax a bit (i go on holiday a week after Jazoon for 2 weeks), and there are more API changes to implement although not of Alpe D'Huez proportions.

Comments:

Congrats to the team.
Very nice work.
I have been using the trunk already and i am very happy with it.

There are many exciting features planned for the 0.8 release. I am specially interested in the injection issues.

Posted by Frank Martínez on April 18, 2008 at 10:14 AM CEST #

Hi Paul,

Great work!

Is there a list of changes from the 0.6 to the 0.7 api posted somewhere?

Rich

Posted by Rich on April 18, 2008 at 11:01 AM CEST #

Hi Rich,

See here:

https://jersey.dev.java.net/source/browse/\*checkout\*/jersey/trunk/jersey/changes.txt?rev=945

Currently it is hand written, but i would really like to automate something that updates for every commit that is specifically marked up.

Paul.

Posted by Paul Sandoz on April 18, 2008 at 11:11 AM CEST #

[Trackback] Last week, before unleashing the Grizzly at ApacheConf 2008, I've traveled to Grenoble to see if we can force a Comet to REST....

Posted by Jean-Francois Arcand's Blog on April 18, 2008 at 12:33 PM CEST #

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