users@jersey.java.net

Fixed Jersey versioning issues with GlassFish

From: Paul Sandoz <Paul.Sandoz_at_Sun.COM>
Date: Mon, 31 May 2010 17:56:41 +0200

Hi,

Out of necessity related to error reporting of injected dependencies i
have fixed Jersey versioning issues with GlassFish.

It is now possible to deploy Jersey version 1.3-SNAPSHOT to the war
and not get strange stack traces because a different version of Jersey
is distributed with GlassFish.

For those interested in technical details heres out it works:

   META-INF/sevices files will be ignored if the corresponding
   META-INF/MANIFEST.MF of the same jar contains a Bundle-SymbolicName
   beginning with "com.sun.jersey" and a Bundle-Version that is not
equal
   to the Bundle-Version declared in the META-INF/MANIFEST.MF for the
same jar
   that contains the com.sun.jersey.spi.service.ServiceFinder.class.

Pavel can you update the GF probes module to include a Bundle-
SymbolicName that begins with "com.sun.jersey"?

There still could be some issues with my implementation, but the
general approach appears to work since any Jersey related jars we
distribute with GlassFish will by necessity require such OSGi-related
attributes in the MANIFEST.MF and we plan to ensure all Jersey modules
are OSGI enabled. Waiting for hudson to report back.

Paul.