Closed GoogleCodeExporter closed 8 years ago
This is the result of an intentional change in GWT 2.7.0 - script loading is no
longer supported in GWT modules using the new default xsilinker. We're
currently investigating how to modify our code to deal with it as cleanly as
possible.
Original comment by smartgwt...@gmail.com
on 25 Nov 2014 at 1:35
We do see the script-loading problem with GWT 2.7.0, which can be worked-around
thusly:
- switch all module inherits to the NoScript (or NoScriptNoTheme where
available) versions
- add explicit <script src="..."></script> load commands to the web page for
those modules for which NoScript (or alternate) versions were introduced above
- shift the DataSource schema load to the web page from the project file (if
present)
For us, the above had to be done with or without SuperDevMode - there was no
difference. We did verify that with these modifications, SuperDevMode seems to
work correctly from Chrome (Chrome 38/Linux x64). We were able to set
breakpoints and hit them.
You may wish to try with one of SGWT Showcases or Sample Projects. (We can
only speculate that you may have been using the old "std" linker for
non-SuperDevMode.)
As far as the ultimate solution, it will not be simple, as we need to
investigate whether GWT (2.7.1?) may provide a fix, and if not, how to best
migrate our module code to use something like the ScriptInjector for script
loading (which is not a "drop in" replacement for the lost funcationality).
Original comment by smartgwt...@gmail.com
on 26 Nov 2014 at 2:43
Thanks for the .SmartGwtNoScriptNoTheme tip - this caused linking to pass.
To get rid of the 404's in the code server I needed to add the following to the
beginning of the <head> on web page:
<script>var isomorphicDir = "[module-name]/sc/"</script>
(the trailing "/" matters).
All is working fine now. Thanks for your help.
Original comment by marcin.n...@crosswordcybersecurity.com
on 29 Nov 2014 at 5:54
To clarify further the notes from post #2, the [...]NoScript modules should be
sufficient to get around the linker limitation in GWT 2.7.0. Use
SmartGwtNoScriptNoTheme only if you want the extra behavior - above and beyond
SmartGwtNoScript which skips loading a skin - that no skins will be copied into
the generated war file.
Original comment by smartgwt...@gmail.com
on 2 Dec 2014 at 4:49
A fix for this issue has been ported back as far as SGWT 4.1p. However, make
sure to note that as mentioned in the SuperDevMode Troubleshooting section:
http://www.smartclient.com/smartgwt/javadoc/com/smartgwt/client/docs/SuperDevMod
eTroubleshooting.html, we still recommend moving away from script tags as
future changes to GWT may lead to additional incompatibilities.
Original comment by smartgwt...@gmail.com
on 26 Feb 2015 at 6:34
Original issue reported on code.google.com by
marcin.n...@gmail.com
on 24 Nov 2014 at 3:41