Hello Oliver, I'd say Spring + some ORM (Ibatis, JPA, Hibernate) are a good deal with GWT. With GWT the server is reduced to a data provider and storage engine. The tasks a server carries out follow always the same pattern:
1. map request to DTOs by interfacing with the client 2. perform validations and access checks 3. perform business logic 4. perform storage 5. return response to the client With a combination of server side frameworks like Spring, Spring security and Hibernate (to mention the established ones) you get steps 1,2,4 and 5 done in no-time (especially if you use AOP), which leaves you to concentrate on the pure business logic. A number of projects have produced libraries, adapters, processes and best practices which combine GWT + your_favorite_framework. So to answer your question: if you're clever you still will use frameworks, just without the web part. If you need workflows, you can use OSWorkflow or Spring Web Flow. On Sep 18, 7:40 am, Oliver Zheng <[email protected]> wrote: > 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. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
