On Sun, Jun 20, 2010 at 4:58 PM, Robson Dantas <[email protected]> wrote:

> Hi guys,
>
> I'm making some experiments using shindig, and I'm quite familiar with PHP
> version. Yesterday, tried to setup Java Shindig, but it was broken. Today
> saw an update on svn which allowed me to compile and run. (mvn and then mvn
> -Prun)
>
> The documentation is a bit outdated and would be great if you provide some
> help:
>
> 1- WARNING: Couldn't load OAuth signing key.  To create a key, run:
>  openssl req -newkey rsa:1024 -days 365 -nodes -x509 -keyout testkey.pem \
>     -out testkey.pem -subj '/CN=mytestkey'
>  openssl pkcs8 -in testkey.pem -out oauthkey.pem -topk8 -nocrypt -outform
> PEM
>
> Then edit gadgets.properties and add these lines:
> shindig.signing.key-file=<path-to-oauthkey.pem>
> shindig.signing.key-name=mykey
>
> gadgets.properties doesn't exist. A similar file which i found is
> shindig.properties, but modifying over there, the message continues to
> appear when starting.
>

config/shindig.properties


>
> 2- I'm getting a 404 message on firebug, with a call to this url:
>
>
> http://localhost:9003/gadgets/js/auth-refresh:core:core.config:core.io:core.json:core.legacy:core.log:core.prefs:core.util:dynamic-height:dynamic-height.util:flash:globals:locked-domain:opensocial:opensocial-0.8:opensocial-0.9:opensocial-base:opensocial-data:opensocial-data-context:opensocial-jsonrpc:opensocial-reference:rpc:security-token:shindig.auth:views:xmlutil.js?container=default


Unclear, any more context?


>
>
> 3- In README file, there's a paragraph:
> Read javascript/README for instructions for using the Shindig Gadget
> Container JavaScript to enable your page to render Gadgets.
>
> But this file doesn't exist, either.
>

Moved to content/README


>
> 4 - To finish it up, gadgets are not being rendered. All app's are showing
> a
> gadgets is not defined message in firebug;
>

Depends on how you're starting things up. Need more context on what's
actually in the gadget render.

--j


>
> Regards,
>
> Robson Dantas
>

Reply via email to