Hi Dustin, Interesting approach, it looks good. Just recently I've blogged about a very similar approach here: http://oktech.hu/blog/2009/07/spring-gwt-integration-with-ease.html
It is not as polished as yours (especially in the documentation part), but a few idea might be interesting for you: 1. Refactoring-compatible addressing, if you convert the package to path (and that way eliminate the need for annotating the impl class) 2. GwtObjectSerializer, which is very handy if you are developing a page that sends the initial data GWT requires in the page embedded. A simple bootstrapping code can extract the object on the client side. The other parts are almost the same. I'd really happy and encourage you to merge my codes into your project if you see them fit somehow. Regards, Istvan On Jul 6, 9:57 pm, "Dustin.Mallory" <[email protected]> wrote: > As a developer who's seen several teams struggle with all the moving > parts involved in GWT on top of Spring, I've started a new project > (http://code.google.com/p/spring4gwt/) that will help tie several > things together. > > First, it provides a simple exporter for Spring services directly > accessible by GWT. This isn't something I invented and in fact has > been done a hundred different ways, but I really like the idea of > seasoned Spring developers being able to drop in a jar, add one entry > to web.xml, and roll, rather than sift through many posts on various > approaches and cobble something together. Plus, it's vital to have > this done consistently for the next part. > > Second, it brings Spring-style dependency injection to the client. > Philisophically it won't be that much different than Gin, only that > it's Spring-flavored instead of Guice. While I've used Gin with great > success, my only complaint is that it doesn't bridge client and server > DI, and that since far more projects are using Spring on the server I > think it makes sense to have a consistent paradigm around annotations, > scope, etc. in both places. After all one of the goals of GWT is to be > immediately accessible to Java developers; I hope to extend that to > RPC and DI with Spring. No "Gin FTW" flames please - I really believe > there is room for both with the continued adoption of GWT throughout > larger applications! > > Item #1 is in the current build with #2 in progress, but I'd love > feedback, especially from those using GWT with Spring, on any other > gaps you think could be made easier when developing GWT on top of > Spring. > > Dustin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
