To dovetail on Ian's points...first decide what you'll need to do and go from there. We don't use a framework per se, but rather we are centered on Spring on the server, and we do a lot of Hibernate too. But these don't really fit the "framework" model especially when it comes to GWT and the client. We love GWT but don't have any real connection between the backend of the server and GWT...which is the way it should be I suppose.
My last tidbit of advice: listen to what Ian says. He's the man! Later, Shaffer On Sep 18, 7:16 am, Ian Bambury <[email protected]> wrote: > Hi Oliver, > Are you approaching this from the right standpoint? Shouldn't you be asking > 'What do I need from a framework?' and then picking a framework? > > The lightest, easiest and simplest framework is no framework at all. All you > really need from the server is services getUserList, updateUserDetails etc. > Very simple stuff. > > Ian > > http://examples.roughian.com > > 2009/9/18 Oliver Zheng <[email protected]> > > > > > > > Hi, > > > I've decided to adopt GWT for an upcoming AJAX-heavy project. The > > requirement on the server-side is that it has to be in Java. What is > > the lightest, easiest to learn, and simplest framework out there to > > use with GWT? All the frameworks I see emphasize how their templates > > are useful, which are pointless with GWT. > > > Thanks.- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
