OAuthClient.access is often a better choice than OAuthClient.invoke, for accessing web services. Give it a try. It was added to the source code -r899, and Maven oauth-core/20090221.
You don't have to use OAuthClient. You can use net.oauth.http.HttpClient, or the Jakarta Commons HTTP software. If you like, you can use OAuthClient for obtaining tokens, and lower level software for accessing protected resources. On Mar 16, 5:53 am, matthias <[email protected]> wrote: > This is clearly a problem with the current implementation. Looking at > the source code of OAuthClient.invoke actually turned up this: > > ... > if (response.getHttpResponse().getStatusCode() != > HttpResponseMessage.STATUS_OK) { > throw response.toOAuthProblemException(); > } > return response; > > This is from a recent build and not acceptable for RESTful Web > services, which frequently answer with success codes other than 200. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OAuth" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/oauth?hl=en -~----------~----~----~----~------~----~------~--~---
