Hi Bjorn!
Sorry that we did not spot the change in the API.
We removed the second parameter since it just confused people. Now you just
need to enter the URL for you validator.
OAuthAuthorizer auth = new OAuthAuthorizer("yourServerValidateURI");
I have updated the example.
You should not try to use the example code as is but you should try to host
your own OAuth authorization server.
Then that's where your protected resource should try to connect to.
It will work with a client store and most likely you should create your own
implementation of client store because the one in internal package is just in
memory store to get you going.
ClientStore clientStore = ClientStoreFactory.getInstance();
clientStore.clientStore("123456789", "secret1", "yourCallbackURI");
If you add a line like this at least you will have one registered client that
can try to access your protected resource.
I will look over the example and make sure it works again.
Having that said I have running code so that You can fetch data and token from
Fb, Google and MS Live using 2.1 RC6. It might help if we also include that
information so that people. can make use of the capabilities. The protected
resource and auth server side has not changed a lot and should be pretty stable.
Please let me know where you think that we should improve in the documentation
and I will try to update it next week.
If you do not want to write you own auth server you could test towards on the I
have on the Internet. Only problem is that the validation interface is
proprietary and others like Apigee have something similar but since its not
standardized you can not have that part portable. (Even if the functionality is
usually extremely similar)
Regards Kristoffer
------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=3011016
