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
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,
I also agree with Ian.
Several frameworks were written to 'fix' problems, I would suggest
trying out some fairly basic GWT's RPC methods. You might even go as
far as calling GWT's RPC a framework.
Cheers,
Scott
--~--~-~--~~~---~--~~
You received this message
I don't really use a framework on the backend either, other than springs DI
+ Ibatis. There's no real need for anything heavy.
On Fri, Sep 18, 2009 at 3:43 PM, Adligo sc...@adligo.com wrote:
I also agree with Ian.
Several frameworks were written to 'fix' problems, I would suggest
trying
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
