Announcement

**Blama** · 28 Sep 2015, 00:46

Hi devmo,

please see these threads. I'm getting the same error.
Isomorphic: This is really annoying when preparing testcases and might also be a real problem for new users. GWT itself is not an easy framework to start using (compared to a java-hello-world). Such problems don't make it easier.

Best regards
Blama

**Isomorphic** · 30 Sep 2015, 09:48

As mentioned in the last reply to the thread you reference, we're not able to reproduce any problem when using asm-3.1.jar. However, when testing with asm-5..0.4.jar, we see a bunch of exceptions from several critical Java apps, including GWT. So shipping an upgraded JAR may lead to users encountering severe problems that they don't have right now.

**DevMo** · 6 Oct 2015, 10:02

Update: I had overlapping issues, ASM + Super Dev Mode config differences in v4 vs v5.

For Smart GWT Eval 5.0 (10/05/2015 build), if I update to asm-5.0.4.jar, the Built-In-DS project runs as expected in Super Dev Mode.

However, for a licensed Smart GWT Power 4.1 (09/30/2015 build), if I update to asm-5.0.4.jar, I still had a bad launch due to...
- Though the console reports success (I think):

Code:

...
   Invoking Linker SmartGwtScriptInjector
      Augmenting builtinds.nocache.js to manually load the following script tags:
sc/initsc.js
sc/modules/ISC_Core.js
sc/modules/ISC_Foundation.js
sc/modules/ISC_Containers.js
sc/modules/ISC_Grids.js
sc/modules/ISC_Forms.js
sc/modules/ISC_RichTextEditor.js
sc/modules/ISC_Calendar.js
sc/modules/ISC_DataBinding.js
sc/skins/Enterprise/load_skin.js
         Link succeeded
         Linking succeeded -- 11.743s
...

...the browser screen is blank, and the Chrome developer console reports

Code:

Uncaught ReferenceError: isc is not defined
Failed to execute 'write' on 'Document': It isn't possible to write into a document from an asynchronously-loaded external script unless it is explicitly opened.
Failed to execute 'write' on 'Document': It isn't possible to write into a document from an asynchronously-loaded external script unless it is explicitly opened.
Failed to execute 'write' on 'Document': It isn't possible to write into a document from an asynchronously-loaded external script unless it is explicitly opened.
Failed to execute 'write' on 'Document': It isn't possible to write into a document from an asynchronously-loaded external script unless it is explicitly opened.
Failed to execute 'write' on 'Document': It isn't possible to write into a document from an asynchronously-loaded external script unless it is explicitly opened.
Failed to execute 'write' on 'Document': It isn't possible to write into a document from an asynchronously-loaded external script unless it is explicitly opened.
Failed to execute 'write' on 'Document': It isn't possible to write into a document from an asynchronously-loaded external script unless it is explicitly opened.
Failed to execute 'write' on 'Document': It isn't possible to write into a document from an asynchronously-loaded external script unless it is explicitly opened.
Failed to execute 'write' on 'Document': It isn't possible to write into a document from an asynchronously-loaded external script unless it is explicitly opened.
Failed to execute 'write' on 'Document': It isn't possible to write into a document from an asynchronously-loaded external script unless it is explicitly opened.
Core SmartClient JavaScript libraries appear not to be loaded.
If inheriting the NoScript SmartGWT modules, verify that the HTML file includes <script src=...> tags to load the SmartClient module .js files from the appropriate location within the WAR.
By default these files are present under [GWT app name]/sc/modules/.
com.smartgwt.client.core.JsObject$SGWT_WARN: Core SmartClient JavaScript libraries appear not to be loaded.
If inheriting the NoScript SmartGWT modules, verify that the HTML file includes <script src=...> tags to load the SmartClient module .js files from the appropriate location within the WAR.
By default these files are present under [GWT app name]/sc/modules/.
at fillInStackTrace_0_g$
at Throwable_2_g$
at Exception_2_g$
at JsObject$SGWT_WARN_1_g$
at init_6_g$
at onModuleLoad_3_g$
at init_2_g$
at initializeModules_0_g$
at apply_0_g$
at entry0_0_g$
at anonymous
at gwtOnLoad_0_g$
at anonymous

Uncaught TypeError: Cannot read property 'Dialog' of undefined

I'm guessing the path provided, "sc/modules/..." to the SmartGwtScriptInjector is incomplete/invalid? Or maybe not? I'm confused because "linking succeeded," but the scripts don't seem to be available to the bootstrap html.

If I manually add the scripts to the bootstrap html as recommended per http://www.smartclient.com/smartgwte...eshooting.html, then the v4.1 project launches as expected.

Code:

<!DOCTYPE html>

<html>
  <head>
    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
    <!--                                           -->
    <!-- Any title is fine                         -->
    <!--                                           -->
    <title>BuiltInDS</title>
    
    <!-- IMPORTANT : You must set the variable isomorphicDir to [MODULE_NAME]/sc/ so that the SmartGWT resource are 
      correctly resolved -->    
    <script> var isomorphicDir = "builtinds/sc/"; </script>

    <!--     Starting with GWT 2.7, scripts cannot be run from inherited modules.  So reference them here. -->
     <script src="builtinds/sc/modules/ISC_Core.js">          </script>
     <script src="builtinds/sc/modules/ISC_Foundation.js">    </script>
     <script src="builtinds/sc/modules/ISC_Containers.js">    </script>
     <script src="builtinds/sc/modules/ISC_Grids.js">         </script>
     <script src="builtinds/sc/modules/ISC_Forms.js">         </script>
     <script src="builtinds/sc/modules/ISC_RichTextEditor.js"></script>
     <script src="builtinds/sc/modules/ISC_Calendar.js">      </script>
     <script src="builtinds/sc/modules/ISC_DataBinding.js">   </script> 
     <script src="builtinds/sc/skins/Enterprise/load_skin.js"></script>

    <!--                                           -->
    <!-- This script loads your compiled module.   -->
    <!-- If you add any GWT meta tags, they must   -->
    <!-- be added before this line.                -->
    <!--                                           -->      
    <script type="text/javascript" language="javascript" src="builtinds/builtinds.nocache.js"></script>
  </head>

  <!--                                           -->
  <!-- The body can have arbitrary html, or      -->
  <!-- you can leave the body empty if you want  -->
  <!-- to create a completely dynamic UI.        -->
  <!--                                           -->
  <body>

    <!--load the datasources-->
    <script src="builtinds/sc/DataSourceLoader?dataSource=supplyItem,animals,employees"></script>

    <!-- OPTIONAL: include this if you want history support -->
    <iframe src="javascript:''" id="__gwt_historyFrame" tabIndex='-1' style="position:absolute;width:0;height:0;border:0"></iframe>

  </body>
</html>

Could you please update the 4.1 template projects to work the same as v5.0 does, with the "loadScriptTagFiles.js" that handles this automatically for Super Dev Mode? Or at least add the individual script references in commented form to the BuiltInDS.html file?

And perhaps update the module DTD reference from GWT 2.5.1 to current 2.7?

If any of the above is misconceived, please set it straight.

Thanks.

**Isomorphic** · 7 Oct 2015, 14:07

The GWT 2.7 SuperDevMode fix for the Eclipse Plugin has been ported back to SGWT 4.1p. It should be in today's nightly (marked 2015-10-07).

**Blama** · 7 Oct 2015, 14:45

Hi DevMo,

the GWT DTD did not change from 2.5.1 to 2.7.0.

Best regards
Blama

**DevMo** · 8 Oct 2015, 10:10

Thanks. Now v4.1 works once I update the ASM JAR.

However, an intervening step is required to get it to launch properly. I'm good to go, I just report this in case it's useful feedback. I don't see this particular case mentioned in the Super Dev Troubleshooting document.

Once the Built-In-DS project is imported, and the ASM JAR is updated:
- right-click Project -> Run As -> Web Application (GWT Super Dev Mode)
- The Eclipse console reports what appears to be good news re linking & compilation succeeded.
- The launched browser is blank, and reports "The page at 127.0.0.1:8888 says: Can't load Datasources - SmartClient runtime not loaded / OK"
- The Chrome console reports:

Code:

Failed to load resource: the server responded with a status of 404 (Not Found)
DataSourceLoader:2 Uncaught ReferenceError: isc is not defined
SuperDevModeLogger.java:71 Core SmartClient JavaScript libraries appear not to be loaded.
If inheriting the NoScript SmartGWT modules, verify that the HTML file includes <script src=...> tags to load the SmartClient module .js files from the appropriate location within the WAR.
By default these files are present under [GWT app name]/sc/modules/. 
SuperDevModeLogger.java:75 com.smartgwt.client.core.JsObject$SGWT_WARN: Core SmartClient JavaScript libraries appear not to be loaded.
If inheriting the NoScript SmartGWT modules, verify that the HTML file includes <script src=...> tags to load the SmartClient module .js files from the appropriate location within the WAR.
By default these files are present under [GWT app name]/sc/modules/. 
  at fillInStackTrace_0_g$
  at Throwable_2_g$
  at Exception_2_g$
  at JsObject$SGWT_WARN_1_g$
  at init_6_g$
  at onModuleLoad_3_g$
  at init_2_g$
  at initializeModules_0_g$
  at apply_0_g$
  at entry0_0_g$
  at anonymous
  at gwtOnLoad_0_g$
  at anonymous
error_1_g$ @ SuperDevModeLogger.java:75log_4_g$ @ SuperDevModeLogger.java:35log_6_g$ @ GWT.java:160log_1_g$ @ GWT.java:247init_6_g$ @ SmartGwtEntryPoint.java:43onModuleLoad_3_g$ @ SmartGwtEntryPoint.java:365init_2_g$ @ com_00046smartgwt_00046sample_00046BuiltInDS__EntryMethodHolder.java:3initializeModules_0_g$ @ ModuleUtils.java:44apply_0_g$ @ Impl.java:247entry0_0_g$ @ Impl.java:306(anonymous function) @ Impl.java:72gwtOnLoad_0_g$ @ ModuleUtils.java:55(anonymous function) @ ValueEnum.java:19
I18nUtil.java:123 Uncaught TypeError: Cannot read property 'Dialog' of undefinedinitMessages_0_g$ @ I18nUtil.java:123init_8_g$ @ I18nUtil.java:32onModuleLoad_3_g$ @ SmartGwtEntryPoint.java:366init_2_g$ @ com_00046smartgwt_00046sample_00046BuiltInDS__EntryMethodHolder.java:3initializeModules_0_g$ @ ModuleUtils.java:44apply_0_g$ @ Impl.java:247entry0_0_g$ @ Impl.java:306(anonymous function) @ Impl.java:72gwtOnLoad_0_g$ @ ModuleUtils.java:55(anonymous function) @ ValueEnum.java:19

Running a compile from the browser via "Dev Mode On" does not improve the situation.

The fix is to run an explicit "GWT Compile Project" (right click Project -> Google -> GWT Compile).

After that, launch the project again from Run Configurations, it'll work then.

**Isomorphic** · 8 Oct 2015, 10:20

Originally posted by Blama View Post

Hi DevMo,

the GWT DTD did not change from 2.5.1 to 2.7.0.

Best regards
Blama

We won't be updating the DTD for old branches, since they must continue to work with old GWT versions and by default those branches are still run with GWT 2.5.1 for our internal testing. For SGWT 5.1, we will update it to GWT 2.6.1, as that's the default GWT version that we test with in that branch. Note that GWT 2.7.0 isn't recommended by default for any branch due to the script tag limitation and associated workaround required.

**DevMo** · 8 Oct 2015, 15:04

Good to know which GWT versions to use, thanks. I had assumed latest was best.

After all that, when I use SGWT v4.1 w/ GWT 2.5.1, there is no ASM error w/ the provided 3.1 JAR.

**stonebranch3** · 14 Jan 2016, 11:58

Isomorphic,

For SGWT 5.1, we will update it to GWT 2.6.1, as that's the default GWT version that we test with in that branch. Note that GWT 2.7.0 isn't recommended by default for any branch due to the script tag limitation and associated workaround required.

Is GWT 2.7.0 still not recommended for SGWT 5.1? I would like to confirm this before upgrading.

Thanks.

**Isomorphic** · 14 Jan 2016, 15:21

At this point, SmartGWT has worked around GWT 2.7's lack of <script> tag support, so it doesn't matter which version you use.

Announcement

Out-of-the-box ASM Error w Super Dev

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment