Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

  • "loadScriptTagFiles.js" is empty

    I am migrating to GWT 2.7.0 in order to use Super DevMode. I tried to run the BuildInDS sample (nothing was changed to it) and got a blank page.

    According to http://www.smartclient.com/smartgwt/...eshooting.html I realized that I need to "Make sure to run the GWT Plugin in Classic Dev Mode at least once, to install the Framework resources and generate loadScriptTagFiles.js." Hence I switched back to GWT 2.6.1, run the sample and the loadScriptTagFiles.js file was generated.

    I switched back to GWT 2.7.0, run the sample and again blank page. The problem is that the loadScriptTagFiles.js file is empty. Why is it empty and how can I correctly generate it?

    I am using Mac OS X 10.10.5, Firefox 53.0.2 (64-bit), Eclipse Kepler Service Release 2, SGWT L5.0 - nightly build from: 2015-09-24. The same happens on other operating systems, with newer versions of Eclipse and other browsers...

    Any hint is appreciated. Thank you!

  • #2
    Originally posted by slick07 View Post
    I realized that I need to "Make sure to run the GWT Plugin in Classic Dev Mode at least once, to install the Framework resources and generate loadScriptTagFiles.js." Hence I switched back to GWT 2.6.1, run the sample and the loadScriptTagFiles.js file was generated.
    No, don't switch back to GWT 2.6.1 - the troubleshooting table didn't say to do that. Just toggle the radio button in the GWT Plugin tab to "Classic Dev Mode" and rerun it. The loadScriptTagFiles.js file will never be generated if you're running GWT 2.6.1.

    Comment


    • #3
      It's normal, in some circumstances, for loadScriptTags.js to be empty.

      Before doing anything else, get the latest patched version. You are 1.5 years out of date.

      Then, if you still have the problem, post more complete information: what's in your host .html file, what error is actually occurring (not just "blank page"), etc.

      Comment


      • #4
        Problem was solved by configuring the GWT Plugin. Thank you! I did not supply any other code related details because I mentioned that I was trying to run the BuildInDS sample.

        Comment

        Working...
        X