Jersey 0.9 is released

We have just released version 0.9 of Jersey. This aligns with the 0.9 release of the JAX-RS API and the editors draft.

For this and further releases the mechanism to obtain Jersey is different. There is no longer one zip file to download. Jersey is now modularized and mavenized thanks to the hard work of Jakub. Jars, source, JavaDoc and samples are all available from the Java.Net maven repo at the following base URI:

http://download.java.net/maven/2/com/sun/jersey/

All the samples can be obtained individually or as one zip file.  

Now it is much easier for maven developers to use Jersey. But as a consequence it is a little harder for non-maven developers to use Jersey. To aid such developers we provide a detailed dependencies document and a bundled jar containing all jersey-related functionality that was previously available in the 0.8 release.

In this release i managed to add support for generic server-side filters and a specific filter to support the "X-HTTP-Method-Override" HTTP header for clients that do not support HTTP PUT and DELETE. Martin has integrated JavaDoclet WADL support. See the example here for more details.

In the past week we have been doing things in parallel and i have been working on the 0.10 implementation before 0.9 is released. We need to step up the pace as the 1.0 finishing line is just a few weeks away.

Comments:

Hi there! Do you think it would be possible to include some documentation on HOW to install jersey? I have been trying to use it... But I cannot figure out how to use it... I am a maven developer, but I find the install instructions confusing at best and I'm not able to get anything done with it :(

Posted by blackHat on September 24, 2008 at 11:55 AM CEST #

Hi blackHat,

To get bootstrapped i recommend looking at pom.xml in some samples [1].

To directly address your issue would it work for you if i modfied [2] to explicit say what dependencies and repositores to add to a pom?

Paul.

[1] http://download.java.net/maven/2/com/sun/jersey/samples/jersey-samples/0.9-ea/jersey-samples-0.9-ea-project.zip
[2] https://jersey.dev.java.net/source/browse/\*checkout\*/jersey/tags/jersey-0.9/jersey/dependencies.html

Posted by Paul Sandoz on September 24, 2008 at 01:10 PM CEST #

Hi Paul,

Wow you respond fast! I cannot even begin to say how helpful this is! But yes, I think that if you added dependencies/repositories to add to a POM that would definitely clear things up for me (and my team). And if possible maybe you could provide a sample ant buildfile as well for a simple project to help new developers get aquainted.

-black

Posted by blackHat on September 24, 2008 at 04:05 PM CEST #

Let me think about the ant example. The reason for my hesitation is we will be going 1.0 very soon... and ant is so very different to that of maven (requiring that jars be available in a different way making this harder to distribute as we do now).

In any case I can take a similar approach as for maven and have a snippet showing the classpath set up for ant.

Posted by Paul Sandoz on September 25, 2008 at 02:24 AM CEST #

The maven ant tasks are very good at integrating maven based projects into ant based based projects.

http://maven.apache.org/ant-tasks.html

We have an older ant build that utilizes the tasks to use maven based projects like Spring.

Posted by Matt Kinman on September 25, 2008 at 11:03 AM CEST #

Matt,

Thanks very much for that link, very useful. I will point to that in the documentation and add some snippets of what to add in an ant file.

Paul.

Posted by Paul Sandoz on September 26, 2008 at 02:09 AM 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