We use GWT in our GAE project for UI stuff, plus RPC to back-end. In GWT you can use third party packages/modules that are packaged into .jar files, and can include Java source for server side, client side Java source (which is used during the GWT compile cycle to produce javascript), native javascripts, image files, css, etc..
We have these GWT jar files in our /lib directory and reference them from our class path, and our external ant build and Eclipse (with GWT plugin) are quite happy with all that. The GWT modules get compile, which generates the compiled javascript and files in the module's 'public' directory (images, css, etc) in / war. So far, so good. If a module has server side code (such as server side of an RPC the client code does, etc), then these .class files must be deployed to the server. Until now we were copying these .jar to our /war/WEB-INF/lib/ for deployment. But I have just realized a few problems with unecessary deployment of files due to that approach: - if a gwt jar (say, gwt-maps.jar) comes with source files (even Javadoc could be in there!) then we will also be deploying that - the client-side java .class files in a library .jar (used to generate javascript) will also be deployed, but never used on the server. I am not sure if that will make our app start-up slowed in AppEngine, or not. Either way, not too nice. What are other people doing in their build/deploy of GAE apps using GWT to avoid such things? -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" 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-appengine-java?hl=en.
