Well, the explanation, in case it is any use to someone else, is this. I had been paring down my previous "multiple entry point" app to having just one entry point. As I wanted only a log in dialog at the outset, I had nothing, or almost nothing, in the RootPanel. I had not planned on instantiating the application window at all until someone validly logged in. All of this worked just swell in the hosted mode.
But the GWT compiler took it to mean that I didn't want to use GWT windows at all, so, I got no initHandlers defined and a blank window when running the app in Tomcat. So I'm refactoring my startup layout. A lesson learned. I figured this out by diff'ing the com.thing.client.EntryPointClass.nocache.js file from my full blown app, and one from a simpler app that was working in Tomcat. "__gwt_initHandlers not defined" means that if you don't request at least one window to exist in RootPanel at startup, the compiler will not define any code to initialize windows, even if you might be wanting to add them later in your app's workflow. In hindsight, makes perfect sense. Might be nice if we had a GWT.dwit() method. Stands for "compiler, do what I'm thinking". Tom --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
