Thanks a lot. Next time, I will read the README first.
But now I´ve got another problem:

I want to open a connection via the android demo app from open social java 
client to get some user details. To do this, I use
the ShindigProvider and set the urls and a new provider

setRestEndpoint("http://server:8081/social/rest/";);
setAuthorizeUrl("http://server:8081/oauth/authorize";);
setAccessTokenUrl("http://server:8081/oauth/accessToken";);
setRequestTokenUrl("http://server:8081/oauth/requestToken";);

addProvider(p, new String[]
{"http://192.168.1.138:8081/samplecontainer/examples/shindigoauth.xml";,
"secret"});

After this I´ve set the scheme in friendlistclass from the demo app
setScheme("http://server:8081/gadgets/oauthcallback";); and edited the
shindigoauth.xml:

<Service name="shindig">
<Request url="http://server:8081/oauth/requestToken";  />
<Authorization
url="http://server:8081/oauth/authorize?oauth_callback=http://server:8081/gadgets/oauthcallback";
/>
<Access url="http:/server:8081/oauth/accessToken"  />
</Service>

Now I get an OAuthException. What did I forget?

Greetings





Am 11.10.2010 16:49, schrieb Christiaan Hees:
In my experience you save yourself a lot of problems if you just run
Shindig as the root tomcat application. If you rename the .war file to
ROOT.war then you can make calls to localhost:8080/social/rest etc. It
might be that Shindig assumes that it's running at the root so you can
try that and see if it works.

On Fri, Oct 8, 2010 at 5:36 PM, Christine Bauers<[email protected]>  wrote:
  hello shindig community

i am trying to use the shindig 2.0 WAR from
http://repo2.maven.org/maven2/org/apache/shindig/shindig-server/2.0.0/shindig-server-2.0.0.war
within a tomcat 6.0 environment and connect an android app to it.

there the trouble starts ;)
the url's are usually "http://localhost:8080/PROJECT/.....";, so if i deploy
my WAR file with the name "shindig.war" the url is:
"http://localhost:8080/shindig/login.jsp"; (for the login-page)

all the url's within the WAR file are relative to "http://localhost:8080/";
(without the PROJECT name), so i had to modify the url's to make the
redirections and location-lookups working.

that all went fine, but now i want to connect via open-social java client
(android app) to shindig.
we are using the following provider-class settings:

setName("localhost");
setVersion("0.8");
setRestEndpoint("http://localhost:8080/shindig/social/rest/";);
setAuthorizeUrl("http://localhost:9090/shindig/oauth-provider/authorize";);
setAccessTokenUrl("http://localhost:9090/shindig/oauth-provider/access_token";);
setRequestTokenUrl("http://localhost:9090/shindig/oauth-provider/request_token";);

but we get an "localhost/127.0.0.1:9090 - Connection refused" exception
(netstat -an shows there is nothing listening on port 9090.. so we tried
port 8080 too, same exception)

if we try to use the default GoogleProvider() class, it works. the code is:

setName("Google");
setVersion("0.8");
setRestEndpoint("http://www-opensocial.googleusercontent.com/api/";);
if (!useRest) {
      setRpcEndpoint("http://www-opensocial.googleusercontent.com/api/rpc/";);
}
setAuthorizeUrl("https://www.google.com/accounts/OAuthAuthorizeToken";);
setAccessTokenUrl("https://www.google.com/accounts/OAuthGetAccessToken";);
setRequestTokenUrl("https://www.google.com/accounts/OAuthGetRequestToken";);
addRequestTokenParameter("scope", getRestEndpoint() + " "
+getRpcEndpoint());

we get redirected to the googlesite, can login and get back to the android
app

so our problems are:
1. is it right that we have to change the project-prefix in every .jsp and
other files to fit the url-scheme "http://localhost:8080/PROJECT/.....";? or
is there a way around that?

2. what could be the reason wyh we get an connection refused (->  tcp conn
not possible??) to localhost:8080 where tomcat is definitely running?

any suggestions would be great

greetings

--
Christine Bauers, Softwareentwicklung


Lyncker&     Theis GmbH
Wilhelmstr. 16
65185 Wiesbaden
Germany

Fon +49 611/9006951
Fax +49 611/9406125


Handelsregister: HRB 23156 Amtsgericht Wiesbaden
Steuernummer: 4023897051
USt-IdNr.: DE255806399

Geschäftsführer:
Filip Lyncker,
Armin Theis




--
Christine Bauers, Softwareentwicklung


Lyncker&   Theis GmbH
Wilhelmstr. 16
65185 Wiesbaden
Germany

Fon +49 611/9006951
Fax +49 611/9406125


Handelsregister: HRB 23156 Amtsgericht Wiesbaden
Steuernummer: 4023897051
USt-IdNr.: DE255806399

Geschäftsführer:
Filip Lyncker,
Armin Theis

Reply via email to