After you've authorized, DesktopClient.access expects Mediamatic to
redirect your browser to its embedded server; that is the Jetty server
to which the local variable access.server refers. The URL is
something like http://localhost:5298/oauth/callback. It sounds like
Mediamatic isn't doing that.
Has Mediamatic upgraded to OAuth 1.0a recently?
On Jul 14, 8:48 pm, monkeyvu <phamanhvu101...@gmail.com> wrote:
> I have run the sample application Mediamatic.java but it's hang at the
> following statement:
>
> accessor.wait();
>
> That statement is in DesktopClient.java file. The snippet of the
> function is:
>
> BareBonesBrowserLaunch.browse(authorizationURL);
> accessor.wait();
> if (accessor.accessToken == null) {
> getOAuthClient().getAccessToken(accessor, null, null);
>
> }
>
> Actually, it opened a new browser with authorization URL, then I got
> the code from the site, enter that code into the running application ,
> close the browser but nothing happened. The application just kept
> running and looks like it's hang...
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"OAuth" group.
To post to this group, send email to oauth@googlegroups.com
To unsubscribe from this group, send email to oauth+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/oauth?hl=en
-~----------~----~----~----~------~----~------~--~---
