O.K. the compiler spits out pretty much everything that was in a public path, so expect to see those in the output (www) directory. in addition you'll likely see some of the following:
[module_name].nocache.js - this is the bootstrap file that loads the actual GWT module. [hash].cache.html - These are the actual javascript payload files tailored for each individual browser/i18n combination. [hash].cache.png - These are generated imagebundle files [hash].gwt.rpc - these are rpc serialization policy files clear.cache.gif - blank gif used by GWT for some tasks history.html - used for history support hosted.html - used for hosted mode support (debugging against a live server) You'll want to deploy all of these. The hosted.html could be omitted, however that would prevent you from stepping through the code running on your live site, so just leave it. -jason On Feb 5, 2009, at 12:14 PM, RussAbbott wrote: > > When I compile my GWT application I get 13 files, including the .html > and .nocache.js files. Apparently these two files are not sufficient > to run the application. (If I launch the .html file in isolation along > with the .js file the application doesn't work.) Does that mean that > when I'm ready to deploy I have to copy the entire generated directory > to my server? > > Thanks. > > -- Russ Abbott > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
