Hi Clanusse, You are right - the only class files that are needed are those that are used by RPC, which are:
-your sync interface -any types that can be passed across the wire over RPC -your server-side classes (including the implementation of your sync interface) Unfortunately, the plugin's deployment mechanism is not smart enough to know which types are purely client and purely server. To do this, the plugin would have to interpret GWT's module information, which it does not do right now. This is a feature that will be available in a future version of the plugin, and at that time, we should be able to "smarten up" the deployment mechanism so that it excludes GWT client classes from war/WEB-INF/classes. Rajeev On Tue, Jun 23, 2009 at 11:08 AM, clanusse <[email protected]> wrote: > > I'm using Eclipse with the Google GAE/GWT plugin to build a combined > GAE/GWT project. I've noticed that Eclipse builds all my classes and > places them in the war/WEB-INF/classes directory even if they are just > GWT client code that also gets crossed compiled to javascript. > > Is this necessary for debugging/development? > > I'm assuming that these GWT client classes aren't used once the > project is deployed to GAE because the client is running the > javascript versions. > > If this is true, Is the GAE Deploy Project plugin smart enough to NOT > push unneeded classes up to App Engine? > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
