Client-side: GWT lets you use Java language, but only a sub-set of the J2SE library, supplemented by a variety of GWT-specific UI classes.
Server-side: You can use whatever you want, including Java. If you wish to use Java (J2EE) on the server, you can - and then the GWT RPC mechanism can be handy. If you wish to deploy to GAE, there are some restrictions - for example, no file access - but the main difference with GAE is how you store data persistently. On Apr 22, 3:35 pm, Danny <[email protected]> wrote: > I am trying to put my application under GWT 1.6, but I am having > problems, because I use some java.awt.image classes. I understand > that Google is working on App Engine for java and has probably not yet > implemented image. > > How can I proceed, since the new eclipse plugins insist on App Engine, > even when I remove the App Engine SDK. > > Any suggestions? > > Danny --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
