Ah.. Something as amiss in what I did. Instead of adding them as flags, the following needs to be added into server.config.
gadget_server_hostname=localhost gadget_server_port=8080 It now points the right server, but there is a different error in esponse that's returned from WIAB's gadget proxy ( http://localhost:9898/gadgets/metadata) {"gadgets":[{"errors":["Missing required container config param, key: gadgets.uri.iframe.basePath, container: wave"],"moduleId":0,"url":"http://localhost:8080/gadget.xml"}]} On Tue, Nov 30, 2010 at 3:41 PM, David Wang <[email protected]> wrote: > Hi Charles, > > On Sat, Nov 27, 2010 at 2:43 AM, cearl <[email protected]> wrote: > >> David, >> Thanks. No, the wiab server & shindig are running on a local network >> for testing. >> So to understand, if I have shindig on localhost1:8080, then I should >> add >> --gadget_server_hostname=localhost1:8080 >> > > I've ran my own shindig with apache server from the instructions at > http://shindig.apache.org/download/index.html#Installation_Instructions. > > The command I used to start WIAB is > > ./run-server.sh --gadget_server_hostname=localhost:8080 > > I've also added a gadget from > http://www.labpixies.com/campaigns/todo/todo.xml and it seems to work. > > > But when I copy the xml into the local tomcat instance so that the gadet's > url looks like http://localhost:8080/todo.xml it doesn't work. > > Looking at the response that's returned from WIAB's gadget proxy ( > http://localhost:9898/gadgets/metadata) I see the following. Could it be > that the shindig server does not not allow fetching from localhost? > > {"gadgets":[{"errors":["Unable to retrieve spec for > http://localhost:8080/todo.xml. HTTP error > 502"],"moduleId":0,"url":"http://localhost:8080/todo.xml"}]} > > > > > >> to command line inside of run-server? >> I'll take a look at the starter project. >> C >> >> On Nov 26, 12:36 am, David Wang <[email protected]> wrote: >> > On Wed, Nov 24, 2010 at 7:08 AM, cearl <[email protected]> wrote: >> > > Is there any advice on gadgets that will work under wiab? For example, >> > > although >> > > http://wave-api.appspot.com/public/gadgets/areyouin/gadget.xml >> > > works fine, I can't seem to get the hello world gadget >> > > http://code.google.com/apis/gadgets/docs/gs.html >> > > running when it is hosted simply in war/static of my wiab server, nor >> > > will gadgets work when hosted on shindig that I am running locally. >> > > That is, the red "Everything's shiny..." alert appears after these >> > > gadgets are loaded. >> > > I'll look more carefully, with the assumption this is something >> > > obvious that I have missed. >> > >> > Is your wiab sever accessible form the internet? >> > >> > How gadgets work is that the client first makes a request to a gadget >> server >> > (a google server) with the gadget XML. the gadget server then fetchs >> your >> > gadget xml file. If your xml file is not accessible on the internet, >> it'll >> > cause the gadget to shiny as no gadget info is returned to the client. >> Btw, >> > the shiny is a bug. The client should simply have a broken jigsaw rather >> > than a shiny. Just to pass on the knowledge around, I've created a >> starter >> > project ( >> http://code.google.com/p/wave-protocol/issues/detail?id=166&q=label:S...) >> > for anyone that's keen to fix this bug :) >> > >> > You can run your own shindig gadget server and make your wiab point to >> it by >> > setting the gadget_server_hostname flag to your host name when you start >> > your WIAB. This is necessary if you don't want to have your XML file >> > accessible on the internet. >> > >> > > C >> > >> > > On Nov 2, 9:01 am, Vega <[email protected]> wrote: >> > > > Thegadgetfrom the url you provided works fine for me in Google Wave. >> > >> > > > On Nov 2, 3:56 pm, Tobias Bachthaler <[email protected] >> > >> > > > wrote: >> > >> > > > > Hey, >> > >> > > > > Thanks for the answer. But if you look at my code, I don't call >> > > > > wave.getState() in init. >> > > > > And I only have a problem after pressing a button, when I call >> > > > > getState() >> > > > > This is long time after initialization and callback registering >> > >> > > > > I remind you also that 1. mygadgetand 2. this demo application >> > > > > counter (FROM THE WAVEGADGETAPI SITE) >> > > > > worked fine until last Friday and I just don't understand why it >> is >> > > > > not working anymore! >> > >> > > > > Please could someone test the testgadgethttp:// >> > > 217.10.12.136:8080/wave/auction2.xml >> > > > > If I do this I get wave.getState() == null >> > >> > > > > Please Google help me I have a presentation of my work Thursday!!! >> > >> > > > > Tobias >> > >> > > -- >> > > You received this message because you are subscribed to the Google >> Groups >> > > "Wave Protocol" group. >> > > To post to this group, send email to [email protected]. >> > > To unsubscribe from this group, send email to >> > > [email protected]<wave-protocol%[email protected]> >> <wave-protocol%2bunsubscr...@goog legroups.com> >> > > . >> > > For more options, visit this group at >> > >http://groups.google.com/group/wave-protocol?hl=en. >> > >> > -- >> > David Wang >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Wave Protocol" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]<wave-protocol%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/wave-protocol?hl=en. >> >> > > > -- > David Wang > -- David Wang -- You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
