Ok, I double checked with my app on several customers domains. All apps running on the new 1.2.6 app engine backend are broken. So gwt is definitely working, but it's not working in conjunction with the new 1.2.6 backend. While 1.2.5 was serving the welcome-page using a real redirect, the new version seems to serve just the content of the welcome page so that all subsequent requests from the gwt locale detection are broken (they go to / instead of /modulename/). My workaround is to implement a RedirectServlet simulating the real redirect to the entry point html page. But this makes all url's look ugly and all of my customers will have to redeploy the app to their Google Apps domains :-(
On 13 Okt., 11:42, dflorey <[email protected]> wrote: > I've a big problem. My GWT app is not working any more since today. > This is what I see from the logs: > Let's say my app module is renamed to "modulename" and I want to > access the app on myapp.appspot.com I have to specify /modulename/ > index.html as welcome page in order to load the app. > This worked fine until today as now the page is accessed properly, but > all gwt resources will not be loaded anymore as they of course reside > in /modulename/... but the gwt loader tries to load them from /... > I don't know if this is because of the upcoming app engine 1.2.6 > release handling > this in a different way or if the gwt-2.x behavior of loading > resources has changed. --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
