Re: undefined.cache.js when starting GWT app in web mode?

2013-10-28 Thread Ed
I am debugging the bootstrap js script to find out what is going wrong and I am a bit confused, please some help? It seems that the bootstrap script throws an exception that is silently ignored, such that the strongName variable is undefined, such that it tries to load undefined.cache.js..

Re: undefined.cache.js when starting GWT app in web mode?

2013-10-28 Thread Ed
I didn't think it would help, but I just added a default browser.engine property to the BrowserEngine.gwt.xml file, just below the define-property...: set-property name=browser.engine value=webkit / !-- provide a default as last resort -- Strange enough this does help, as it does starts now.

Re: undefined.cache.js when starting GWT app in web mode?

2013-10-28 Thread Colin Alworth
If you compile in PRETTY instead of DETAILED, it won't intern those strings, but still will leave the output mostly readable (just no packages). Without seeing the rest of the structure of the module files, it is hard to speculate, but we're using more or less the same idea successfully, though

Re: undefined.cache.js when starting GWT app in web mode?

2013-10-28 Thread Ed Bras
@Colin: thanks for isolated example that shows the problem. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: undefined.cache.js when starting GWT app in web mode?

2013-10-28 Thread Colin Alworth
Looks like my sample may have been too simplistic - upon re-reading http://code.google.com/p/google-web-toolkit/wiki/ConditionalProperties it looks like they do indeed suggest using a default as the 'correct' way to do things: !-- Provide a default -- set-property name=alternateFeatures