On Oct 19, 2009, at 1:00 PM, Á. Eduardo García wrote:
> Hi, and thanks Paul.
>
> However, I'm seeing the modified file being 1.1.5 instead of 1.1.4.
> Is that version what you mean? It's ok for me, that's the one I'm
> using anyway :)
I committed the fix to:
branches/jersey-1.1.4-ea-SNAPSHOT/
trunk/jersey/
We are currently maintaining a 1.1.4-ea-SNAPSHOT branch for the
version of Jersey that will be distributed with the final release of
GlassFish v3. The trunk is at 1.1.5-ea so we can include additional
features since 1.1.4-ea will only include changes for bug fixes.
In another email you stated:
> I've used Jersey 1.1.5 (but I don't know if it's in use, because
> Glassfish itself has Jersey 1.1.3 in it's own libraries, and when I
> start the server it says something like:
>
> INFO: Initiating Jersey application, version 'Jersey: 1.1.3-ea
> 10/06/2009 05:16 PM'
I guess you are using something like build 66 or greater of GlassFish?
If you set the class loader delegation to false in the sun-web.xml
things should work. Note that you might get some additional exceptions
logged, which should be harmless.
The general problem is because Jersey uses META-INF/services it is
hard to isolate the version of Jersey distributed in GlassFish and the
version of Jersey distributed in the war. There is a potential fix
using a special OSGi web deployment feature of GlassFish but that
solution requires more work from GlassFish.
If you like you could try to remove Jersey from GlassFish using the
update center tool. Note that for every stable release of Jersey we do
distribute it to the update center so it should be possible to upgrade
via GlassFish.
Hth,
Paul.
---------------------------------------------------------------------
To unsubscribe, e-mail:
[hidden email]
For additional commands, e-mail:
[hidden email]
