Hi there,
I've been migrating an application from GWT 2.5 to GWT2.8b1. After working around how to debug in Super Dev Mode and getting the app to run relatively smoothly, we've encountered an odd issue in the generated JS code which does not show up when debugging:
Stack Trace from Chrome:
Uncaught TypeError: $wnd.MY_MODULE_LAUNCHER.runAsyncCallback7 is not a function
(anonymous function) @ VM420:1
MY_MODULE_LAUNCHER.__installRunAsyncCode @ MY_MODULE_LAUNCHER.nocache.js:11
__gwtInstallCode @ MY_MODULE_LAUNCHERr-0.js:1
hSn @ MY_MODULE_LAUNCHER-0.js:15518
XSn @ MY_MODULE_LAUNCHER-0.js:14712
YSn.b.onreadystatechange @ MY_MODULE_LAUNCHER-0.js:15550
Problematic line (referenced as VM420:1 above):
$wnd.MY_MODULE_LAUNCHER.runAsyncCallback7("VERY_VERY_LONG_STRING_OF_JS_CODE_HERE");
I've removed all the code-splitting (GWT.runAsync()) from the application and this JS error disappears, which gets us moving for now but I'm wondering:
- is this a regression bug? This had worked fine in GWT 2.5. Bug to be fixed because it is beta?
- is this just a change in GWT.runAsync I missed somewhere?
- Am I just bad at code-splitting/GWT.runAsync and this is a case of user error?
- Infamous "other"
Thanks for any input/feedback.
-- I've been migrating an application from GWT 2.5 to GWT2.8b1. After working around how to debug in Super Dev Mode and getting the app to run relatively smoothly, we've encountered an odd issue in the generated JS code which does not show up when debugging:
Stack Trace from Chrome:
Uncaught TypeError: $wnd.MY_MODULE_LAUNCHER.runAsyncCallback7 is not a function
(anonymous function) @ VM420:1
MY_MODULE_LAUNCHER.__installRunAsyncCode @ MY_MODULE_LAUNCHER.nocache.js:11
__gwtInstallCode @ MY_MODULE_LAUNCHERr-0.js:1
hSn @ MY_MODULE_LAUNCHER-0.js:15518
XSn @ MY_MODULE_LAUNCHER-0.js:14712
YSn.b.onreadystatechange @ MY_MODULE_LAUNCHER-0.js:15550
Problematic line (referenced as VM420:1 above):
$wnd.MY_MODULE_LAUNCHER.runAsyncCallback7("VERY_VERY_LONG_STRING_OF_JS_CODE_HERE");
I've removed all the code-splitting (GWT.runAsync()) from the application and this JS error disappears, which gets us moving for now but I'm wondering:
- is this a regression bug? This had worked fine in GWT 2.5. Bug to be fixed because it is beta?
- is this just a change in GWT.runAsync I missed somewhere?
- Am I just bad at code-splitting/GWT.runAsync and this is a case of user error?
- Infamous "other"
Thanks for any input/feedback.
You received this message because you are subscribed to the Google Groups "GWT Users" 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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment