Although I applied the patches referred to at
http://codereview.waveprotocol.org/375001
and made the changes to run-config (on the wiab) and in container.js
( shindig) I am still getting the shiny:
I'll try with latest version of the wiab.
Stacktrace:
(TypeError): Cannot call method 'replace' of null
stack: TypeError: Cannot call method 'replace' of null
at $replaceFirst (http://charles-earls-macbook-pro.local:9898/
webclient/7AA797FE22E8C2F75D3BFA6C1FFE661B.cache.html:3042:81)
at $parse_0 (http://charles-earls-macbook-pro.local:9898/webclient/
7AA797FE22E8C2F75D3BFA6C1FFE661B.cache.html:9997:88)
at Object.GadgetMetadata_0 (http://charles-earls-macbook-pro.local:
9898/webclient/7AA797FE22E8C2F75D3BFA6C1FFE661B.cache.html:10033:43)
at Object.onResponseReceived (http://charles-earls-macbook-
pro.local:9898/webclient/7AA797FE22E8C2F75D3BFA6C1FFE661B.cache.html:
9615:16)
at $fireOnResponseReceived (http://charles-earls-macbook-pro.local:
9898/webclient/7AA797FE22E8C2F75D3BFA6C1FFE661B.cache.html:380:68)
at Object.onReadyStateChange_0 [as onReadyStateChange] (http://
charles-earls-macbook-pro.local:9898/webclient/
7AA797FE22E8C2F75D3BFA6C1FFE661B.cache.html:731:112)
at XMLHttpRequest.<anonymous> (http://charles-earls-macbook-
pro.local:9898/webclient/7AA797FE22E8C2F75D3BFA6C1FFE661B.cache.html:
26171:74)
at apply (http://charles-earls-macbook-pro.local:9898/webclient/
7AA797FE22E8C2F75D3BFA6C1FFE661B.cache.html:2743:80)
at entry0 (http://charles-earls-macbook-pro.local:9898/webclient/
7AA797FE22E8C2F75D3BFA6C1FFE661B.cache.html:2799:38)
at XMLHttpRequest.<anonymous> (http://charles-earls-macbook-
pro.local:9898/webclient/7AA797FE22E8C2F75D3BFA6C1FFE661B.cache.html:
2780:20)
type: non_object_property_call
arguments: replace,
Unknown.$collect (JsArrayString.java:42)
Unknown.fillInStackTrace_2 (StackTraceCreator.java:146)
Unknown.fillInStackTrace_0 (StackTraceCreator.java:386)
Unknown.fillInStackTrace (Throwable.java:72)
Unknown.$$init_16 (Throwable.java:46)
Unknown.Throwable_0 (Throwable.java:49)
Unknown.Exception_0 (Exception.java:25)
Unknown.RuntimeException_0 (RuntimeException.java:25)
Unknown.JavaScriptException_0 (JavaScriptException.java:127)
Unknown.caught_0 (Exceptions.java:29)
Unknown.$replaceFirst (String.java:848)
Unknown.$parse_0 (GadgetMetadata.java:163)
Unknown.GadgetMetadata_0 (GadgetMetadata.java:85)
On Dec 2, 9:57 pm, David Wang <[email protected]> wrote:
> On Fri, Dec 3, 2010 at 1:45 PM, David Wang <[email protected]> wrote:
> > Yeah.. I got gadget's working through a locally running shindig.
>
> > Adding to Anthony have sent out, I've just sent out a fix for WIAB
> >http://codereview.waveprotocol.org/375001that should now have gadgets
> > working for Safari/Chrome. Gadgets in FF3.x is still broken. It seems as
> > though the ifpc is broken there.
>
> > This change list also contains a work around for a bug in wave.js shindig.
> > It looks like a java comment in wave.js from shindig contains the text
> > "<code>" which break the js on the browser.
>
> > I'll write up a wiki page on how to get gadget working with your own
> > shindig server.
>
> The instruction is now up
> athttps://sites.google.com/a/waveprotocol.org/wave-protocol/code/tutori...
>
>
>
>
>
>
>
>
>
>
>
> > Kind Regards
>
> > On Wed, Dec 1, 2010 at 2:25 AM, antwatkins <[email protected]> wrote:
>
> >> David a couple of things to try:
>
> >> make sure wave is added to your list of containers in shindig. Go to
> >> the WEB-INF/classes/containers/default/containers.js and add "wave" to
> >> "gadgets.container" property.
> >> "gadgets.container" : ["default", "accel", "wave"],
> >> Note: I believe the desired method is to create your own custom
> >> containers.js file and not edit default, but I edited the default.
>
> >> Another issue you may come across is that wave doesn't use the
> >> security token (st), so you have to set shindig not to require it. In
> >> the container.js file referenced above add the line:
> >> "render_token_required" : false,
> >> Note: this above line means people can use your gadget server to
> >> render gadgets without knowing the security token. So some other
> >> firewall/security mechanism will have to be put in place.
>
> >> R,
>
> >> Anthony
>
> >> On Nov 30, 12:21 am, David Wang <[email protected]> wrote:
> >> > 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.xmlandit seems to work.
>
> >> > > But when I copy the xml into the local tomcat instance so that the
> >> gadet's
> >> > > url looks likehttp://localhost:8080/todo.xmlitdoesn'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
> >> forhttp://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%2bunsubscr...@goog
> >> > >> > > legroups.com>
> >> <wave-protocol%2bunsubscr...@goog legroups.com>
> >> > >> <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%2bunsubscr...@goog
> >> > >> legroups.com>
> >> <wave-protocol%2bunsubscr...@goog legroups.com>
> >> > >> .
> >> > >> 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]<wave-protocol%2bunsubscr...@goog
> >> legroups.com>
> >> .
> >> 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.
