Ah, makes sense. I think I was confused because I got the trunk of jersey and had some issues with deployment, kept saying it couldn't find ApplicationConfig class or something. I thought it was because I was using the ServletContainer from the helloWorld webapp example, so I went back to ServletAdapter and that didn't seem to fix it either. Honestly I might have mixed up jsr311 and jersey versions at that point. I am now using .9 and seems to work for now. Can't wait for the 1.0 final!
----- Original Message ----
From: Paul Sandoz <Paul.Sandoz_at_Sun.COM>
To: users_at_jersey.dev.java.net
Sent: Monday, August 18, 2008 12:14:20 AM
Subject: Re: [Jersey] Where did ApplicationConfig go in the .10 jsr311 library?
Hi Kevin,
The Jersey version is kept in sync with the 311 version. So for Jersey 0.9 you need to use 311 0.9. If you are using Maven then it is easy as the dependencies are done for you.
The Jersey stable releases are always a bit behind the 311 releases as it takes time to implement the API changes from one release to the next.
0.9 will be released at the end of the week.
Work on .10 is likely to start this week in parallel with the 0.9 release as we are getting closer to our deadline and we need to verify and give the opportunity for others to verify as well that such .10 changes are working and are effective.
Paul.
On Aug 18, 2008, at 1:46 AM, Kevin Duffey wrote:
Ok, I figured it out.. after several tries I was able to find in the svn logs that it was renamed. Is there a rough idea when the jersey will build with jsr311?
Thanks.
----- Original Message ----
From: Kevin Duffey <andjarnic_at_yahoo.com>
To: users_at_jersey.dev.java.net
Sent: Sunday, August 17, 2008 4:03:53 PM
Subject: [Jersey] Where did ApplicationConfig go in the .10 jsr311 library?
Hello all,
So I thought I'd be hip by grabbing the latest jsr311 source, and building it, and then the latest jesey and building that. Turns out, I get some nasty deployment issue with this ApplicationConfig class no longer being found. My guess is that Jersey doesn't just yet implement the proposed final draft? I grabbed the source of both this morning, so that is the only conclusion I can come to at this point. If this is indeed the issue, when will Jersey support the final draft? I guess in the meantime I gotta grab the .9 jsr311 jar to get something working. :(