Well, once again, thank you Scott !!
> Is this running on Debian? Console output was redirected > to /var/log/syslog by default, and didn't show up in catalina.out. > > No it a CentOS but I am not using the default Tomcat package but a tar.gz file from Tomcat (apache-tomcat-6.0.24). Nothing in /var/log/syslog or /var/log/messages The "weather" widget does this, so would be worth trying. > Well, he "weather" widget doen't work for me. There'is nothing in the log (catalina.out) > > Note that the widget access policy is currently only loaded when the widget > is dropped into the "deploy" folder, and not when added through the "admin" > web interface. > > If I am right, the weather widget was dropped into the deploy folder > Look for a line in the log (or catalina.out, or syslog...) that says > something like: > > 11:12:14,753 INFO WidgetFactory:213 - access policy granted for tweetWatch > to access http://twitter.com > 11:12:14,754 INFO ContextListener:178 - tweetWatch' - Widget was > successfully imported into the system. > > The other thing is about using Google Gadgets under wookie. I have'nt been > successfull with this. > I have tried importing this hello-the-world gadget : > http://people.portaildulibre.fr/~afutschik/bonjour.xml<http://people.portaildulibre.fr/%7Eafutschik/bonjour.xml>without > success. > > > It would appear that your Shindig server is not available at the location > set in your configuration? > Well, actually, I did not install any Shinding server. I am not sure what this is. > > I managed it OK with my setup, so there is nothing wrong with your gadget: > I can see that :) Thanks for testing ! > > > For simplicity, I usually install Shindig as the Tomcat root webapp and > then have wookie configured as follows: > > # Location of Shindig services > widget.shindig.url=/ > widget.metadata.url=/gadgets/metadata > > (Note that Shindig isn't installed by default with Wookie, you need to go > to the Shindig project and get the .war file.) > I'll try and install it and come back to you. Adrien
