Export to GitHub

google-web-toolkit - issue #9226

Module won't load

Posted on Jul 21, 2015 by Happy Giraffe

Found in GWT Release (e.g. 2.4.0, 2.5.1, trunk):

GWT 2.0

Encountered on OS / Browser (e.g. WinXP, IE9, FF10):

MacOSX Yosemite Chrome and Safari

Detailed description (please be as specific as possible):

The modules in my project won't load when I visit each of my html pages.

Shortest code snippet which demonstrates issue (please indicate where actual result differs from expected result):

<code> <head> <meta http-equiv="content-type" content="text/html; charset=UTF-8">

&lt;title&gt;Comments - Elaine's Sweet Life&lt;/title&gt;
&lt;link href=&quot;Main.css&quot; rel=&quot;stylesheet&quot;&gt;

&lt;script type=&quot;text/javascript&quot; language=&quot;javascript&quot; src=&quot;Comments/Comments.nocache.js&quot;&gt;&lt;/script&gt;

</head> </code>

<code> <!DOCTYPE module PUBLIC "-//Google Inc.//DTD Google Web Toolkit 2.0//EN" "http://google-web-toolkit.googlecode.com/svn/releases/2.0/distro-source/core/src/gwt-module.dtd"&gt; <module rename-to='Comments'>

&lt;inherits name='com.google.gwt.user.User'/&gt;
&lt;source path='client'/&gt;
&lt;entry-point class='com.elainesSweetLife.client.entry.Comments'/&gt;

</module> </code>

The error:

[WARN] 404 - GET /Comments/Comments.nocache.js (127.0.0.1) 1393 bytes Request headers Host: 127.0.0.1:8888 Connection: keep-alive Accept: / User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_4) AppleWebKit/600.7.12 (KHTML, like Gecko) Version/8.0.7 Safari/600.7.12 Accept-Language: en-us Referer: http://127.0.0.1:8888/Comments.html Accept-Encoding: gzip, deflate Response headers Content-Type: text/html;charset=ISO-8859-1 Cache-Control: must-revalidate,no-cache,no-store Content-Length: 1393

Links to relevant GWT Developer Forum posts:

http://www.gwtproject.org/doc/latest/DevGuideOrganizingProjects.html

Comment #1

Posted on Jul 23, 2015 by Swift Rhino

Please note that the issue tracker has moved to GitHub: http://www.gwtproject.org/lifeofanissue.html

Before reopening an issue there, I would however first:

Status: Invalid