Monday, October 28, 2013

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

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.
The code to determine the strong name has changed to:
 strongName = answers[computePropValue($intern_47)][computePropValue($intern_58)];

As you can see the "browser.engine" property has been removed as argument. Before it was:
 strongName = answers[computePropValue($intern_47)][computePropValue($intern_48)][computePropValue($intern_59)];

Why this difference?
btw: it seems to work in both chrome/FF.

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.

No comments:

Post a Comment