On 06/24/2010 07:12 PM, Paul Sandoz wrote:
>
> On Jun 24, 2010, at 10:07 AM, Jakub Podlesak wrote:
>>>
>>> But is the activator used for the GF OSGi environment?
>>
>> That is a very good question. I believe it is the key to the issue.
>> As GF environment uses the class-loading magic, jersey modules
>> META-INF/services files are visible to the JSR311 bundle.
>> We were relying on that functionality until 1.2,
>
> Up to and including 1.2?
yes, even when that version contained the individual osgified modules,
the glassfish module still contained the "gf-osgified" uber jar
that is why the admin tests started failing after 1.3 integration only
>
>
>> where we used to bundle one big jersey uber jar with GF.
>>
>> Then we broke jersey down to the individual modules and introduced
>> the activators, which made jersey to work in a generic OSGi runtime
>> (testing on grizzly/jetty/felix/equinox).
>>
>> Now in GF, the two approaches are probably clashing.
>> I believe the old class-loading magic is still in place?
>>
>
> I presume so, and the activator is not kicking in for web deployments?
no, at least our tests with jersey samples deployed as wars onto GF with
the latest jersey are passing [1]
~Jakub
[1]
http://sysifos-sol.czech/hudson/job/Jersey-test-GFv3-tests/
>
> Paul.