There is also the GWT Server Library from the GWT Widget Library project: http://gwt-widget.sourceforge.net/
You should also check out the support for GWT that is now built into Spring Roo. If you already use (or want to use) the technologies that Spring Roo builds in, like JPA, then Roo will get you running fast with a solid architecture that uses best practices: http://www.springsource.org/roo http://blog.springsource.com/2010/05/19/spring-roo-1-1-0-m1-released/ http://blog.springsource.com/2010/06/02/using-springsource-tool-suite-2-3-3-m1-with-roo-and-gwt/ I don't think there is one right answer to your question. How you use Spring with GWT depends on your project and your team's preferences. However, it is quite useful using Spring MVC (or some other Java web framework) with GWT because GWT doesn't provide much server-side facilities. In a large project, you are likely to need some static web pages that do not use GWT, and Spring MVC makes that easy (among many other things). Additionally, we have used Spring MVC controllers for file upload and download, and to serve up resources from the classpath. I also believe it is very useful to avoid having your actual service implementation extend from GWT's RemoteServiceServlet. Spring MVC allows your controllers to be implemented as POJOs, and most Spring- GWT integration libraries strive to allow you to use GWT RPC while still implementing your services as POJOs. Some benefits to this approach are the ease of unit testing POJOs and no dependence on GWT libraries in your services. Hope that helps, -Richard On Jun 8, 11:32 am, ezamur <[email protected]> wrote: > Hi all... > > I am new to GWT - had some contact with it earlier but not enough to > say I am confident with it. > > My task is to investigate this technology and pair it with Spring > framework. There are a lot of tutorials explaining how this can be > done, but what is bothering me is I can't decide which approach to > choose. For example, I've seen one using Spring's MVC (like this > one:http://technophiliac.wordpress.com/2008/08/24/giving-gwt-a-spring-in-...), > but also other where integration is done without it > (e.g.http://code.google.com/p/gwt-spring-starter-app/) > > I am afraid to miss something important by choosing one of these > approaches and possibly lose some of Web MVC functionalities that > might be needed later or end up in dead end street using it. > > I would be grateful if anyone explained me what are the pros and cons > of these approaches from practical point of view - is there a need for > DispatcherServlet and Controllers while having GWT and its RPC > mechanism. > > Thanks in advance. -- 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.
