[markok]

Happened to me too (gwt2, upgraded smartgwt 2.1 -> 2.2). I has using SmartGwtNoTheme and inheriting Graphite explicitly.

Got it working though by explicitly forcing
...
<script>var isomorphicDir = "sc/";</script>
...

.. In my html file. I didn't have this before and it was working fine - funny though that now it seems to need it although the feature addition aimed getting rid of it :) The reason was same as other users, duplicate application context in url's ending up for theme resources not loading correctly.

[markok]

You configuration was invalid in the fist place. You cannot inherit SmartGwt and the Graphite modules since the SmartGwt module inherits the default Enterprise skin and there are bound to be conflicts.

Only you know the details of your environment. We have no idea what



means. So spend some time comparing your setup with the HelloWorld setup that was indicated in my previous post and figure out the problem.

It means that for some reason the application is trying to load theme resources of "my.Application" named module from http(s)://server:port/appcontext/my.Application/my.Application/sc/skins/EnterpriseBlue/... when the correct url should be http(s)://server:port/appcontext/my.Application/sc/skins/EnterpriseBlue/...

The problem goes away and latter url's are used when explicitly defining the isomorphicDir var.

[smartgwt.dev]

Happened to me too (gwt2, upgraded smartgwt 2.1 -> 2.2). I has using SmartGwtNoTheme and inheriting Graphite explicitly.

Got it working though by explicitly forcing
...
<script>var isomorphicDir = "sc/";</script>
...

.. In my html file. I didn't have this before and it was working fine - funny though that now it seems to need it although the feature addition aimed getting rid of it :) The reason was same as other users, duplicate application context in url's ending up for theme resources not loading correctly.

Please post a minimal standalone testcase similar to the helloworld sample that illustrates this problem. Until you do so, we cannot do much to help.

[markok]

Please post a minimal standalone testcase similar to the helloworld sample that illustrates this problem. Until you do so, we cannot do much to help.

Replicated it with your helloworld-2.0 example bundled with the distribution with minor changes.

The problem has to do with how you package your app. In your helloworld the html file is in the web application root and includes the compiled .js from the application directory helloworld/. If your html file is in the gwt modules public/ dir it fails. This is the way I'm used packaging my apps - I use the gwt's public dir and load the app from <context>/modulename/ directory with browser.

Step to re-produce with the helloworld-2.0 example:

1. create src/com/mycompany/public dir
2. move war/HelloWorld* to src/com/mycompany/public
3. edit HelloWorld.html to include the .js file from the current dir (remove helloworld/)
4. ant clean war, deploy to your preferred container
5. open http://.../HelloWorld/helloworld/ to your browser

I suspect why my apps have worked without the explicit isomorphicDir variable is that the library defaults to looking at sc/ ? As I load the app from the module root the skins are always found from sc/.

Btw, the web.xml in your helloworld example is not 100% by the spec and fails to deploy atleast to glassfish. The welcome-file-list element should come after the servlet declarations.

br,
Marko

[smartgwt.dev]

The new "war" directory structure support that was introduced in GWT has the host html in the web root so users don't have to hit a URL like http://.../com/mycompany/HelloWorld.html

Smart GWT 2.2 eliminates the need for setting isomorphicDir when using the default "war" directory structure. You're using a non standard location for the host html file so you'll still need to set isomorphicDir. We'll add a note about this for the next release.