Comments on: Non invasive GWT and Spring integration

By: P.G.Taboada

P.G.Taboada — Mon, 21 Sep 2009 14:03:09 +0000

Here another update:

Have a look at http://pgt.de/2009/09/18/best-practices-for-architecting-your-gwt-app/

By: José

José — Tue, 04 Aug 2009 08:09:05 +0000

gwt-sl library works well without giving up the development shell or Tomcat.

By: Non invasive GWT and Spring integration (reloaded) | pgt

Non invasive GWT and Spring integration (reloaded) | pgt — Fri, 17 Jul 2009 20:17:01 +0000

[...] invasive GWT and Spring integration (reloaded) New project layoutHere is my overdue update to my Non invasive GWT and Spring integration blog post from early 2008. Since then we have had the GWT 1.6 and GWT 1.7 releases: One of the [...]

By: Iwein Fuld

Iwein Fuld — Wed, 16 Jul 2008 17:13:57 +0000

Great stuff! Yet another custom built solution… it’s about time that either the Spring Framework or GWT packages a complete solution for this. Maybe you could simplify using @Configurable? http://is.gd/V5s.

By: Papick G. Taboada

Papick G. Taboada — Fri, 15 Feb 2008 12:10:59 +0000

If you are already using Spring 2.5, you should also read:

http://blog.digitalascent.com/2007/11/gwt-rpc-with-spring-2x_12.html

This is another integration strategy that uses the new @Component Annotation and Springs new component scanning features.

Great work!

The only problem here is that (if we stick to the embeded Tomcat and the Developmentshell provided out of the box) we get two servlets listening to the same url: the one generated by the Development Shell startup (remember: the web.xml gets re-generated), and the one started as a @Component by Spring.

If we had some way to turn off the generation of the web.xml we could bypass this problem…