Solved it! Lothar, you were on the right track.
Turns out giving GWT modules a name that starts in an uppercase letter is a very bad idea... What happens is that when it get's packaged in the war file, all package parts (a.b.c.moduleName) will be converted to start with a lowercase. This leads to 404's where files like '...nocache.js' are not found. Hope someone else finds this and spares themselves a frustrating day of fiddling with war files ;) Jaco On Jan 19, 8:31 pm, Lothar Kimmeringer <[email protected]> wrote: > superkruger schrieb: > > > In hosted mode the app works fine, but as soon as I package it into a > > war and deploy to tomcat or jboss, the onModuleLoad never get's called > > and the container reports no problems. > > What gets displayed is the entrypoint html file contents, but > > obviously none of the div contents. > > Check the logfiles of Tomcat, especially the request-log. > Maybe some files - like the Javascript-file - are not found > (leading to a 404-entry in the requets-log). > > Regards, Lothar --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
