If you want to use GWT RPC for client server communication, there is no need
for Spring Web MVC. If you want to provide a RESTful API and use it for GWT
too, Spring Web MVC is a good choice for realizing RESTful APIs.

Regards
Jan Ehrhardt

2010/6/13 Stefan Bachert <stefanbach...@yahoo.de>

> Hi,
>
> Spring MVC does not fit to GWT at all.
>
> GWT considers the browser to be a thin/rich client, and the server to
> be the data source/model
>
> Spring MVC considers the browser to be an ultra thin client (something
> like an x-server), and considers the "server" to be a fat client,
> where presentation, business logic and persistence live.
> Spring MVC is an artefact of the pre-AJAX-era.
>
> Use GWT for real application (RIA) and use Spring MVC for hyperlinked
> documents.
>
> In a complex website you may switch between real applications and
> hyperlinked documents, so you will find both in one site.
> But it makes NO sense to drive GWT with Spring MVC.
>
> When you look at Spring Roo and its GWT support, it comes without
> Spring MVC (Spring Roo can generate Spring MVC controller but without
> GWT). It is "either or"
>
> Stefan Bachert
> http://gwtworld.de
>
>
> On Jun 8, 5:32 pm, ezamur <eza...@gmail.com> 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 google-web-tool...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com<google-web-toolkit%2bunsubscr...@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Reply via email to