Hi Matthias,
I've found another workaroud. You can simply copy-paste the
META-INF/services directory from the jersey oauth modules directly to
your application - then it should work. This issue is now tracked here:
http://java.net/jira/browse/JERSEY-772
I added the workarounds there. Seems this is a regression that was
introduced with Jersey 1.8 into GlassFish 3.1.1.
Martin
On 6.9.2011 12:14, Martin Matula wrote:
> What version of GlassFish are you using?
> This looks like the signature classes are not visible to the OSGi
> locator. We have to investigate this further.
> In the meantime, the following steps will make it work:
> 1) include all the other jersey jars your app depends on in the war
> file of your application
> 2) follow the instructions on overriding Jersey included in GF with
> Jersey included in your war file:
> http://jersey.java.net/nonav/documentation/latest/glassfish.html#d4e1927
> 3) restart GF
> 4) redeploy your app
> Regards,
> Martin
>
>
> On 5.9.2011 20:47, me_at_matthiasb.com wrote:
>> I put oauth-client-1.8.jar, oauth-server-1.8.jar, and
>> oauth-signature-1.8.jar into the WEB-INF/lib folder which gets deployed
>> to the glassfish server. All of the oauth specific classes are
>> available, only the signatures seem to be missing (but the jar file is
>> present). Are there additional jars that I shold put on the classpath?
>>
>> Thanks for your help,
>> Matthias