Your simple case is not quite what I'm referring to. Take instead your simple case, but you have to recompile everything. However, when you deploy, because you didn't optimize, and because you've separated your reusable code into separate libraries, you will have identically named files that each sub-app if you will can share. There is potentially some need for creative code splitting there so that the libraries are actual files to download, but those filenames are based on an md5 sum as I recall, so if the same content is in there, they are the same file.
The reason I say optimization would need to be turned off is so that you don't get a different file generated by the compiler. Essentially giving you every library call a sub-app could use. Very much like the prototype or jquery model. Ultimately, it's not the way GWT was intended to be used, but you'd still get the Java development environment and the permutation logic which is pretty big in the web world, so you *could* do it. -- 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.
