Hi, My Humble experience on the subject.
It's quite easy to dispatch GWT RPC to Spring Managed Bean (SMB). There are 2 main strategies: 1) consider the SMB as a technical wrapper to a business service and then let SMB depend (implementing) on RemoteService. ++ No configuration ++ No naming convention - - technical dependencies from SMB to GWT Remote service. 2) consider the SMB as *the* business service and let spring map/dispatch the GWT request to the SMB. -- Configuration OR naming convention ++ No a technical dependencies from SMB to (GWT) RemoteService. On my project I've choose the 1): http://code.google.com/p/net-orcades-spring/ but I could (and surely will :) implement the 2) as soon I found a clever way to map gwt service to SMB with a minimal of configuration / convention. GWT Widget choose the 2) http://gwt-widget.sourceforge.net/ On Fri, Nov 7, 2008 at 7:29 PM, Allen Firstenberg <[EMAIL PROTECTED]> wrote: > > I've gone through the documentation, and while I see a lot of "here is > how you can do it with spring", most seem to be referencing hacks and > work-arounds that were necessary in 1.3. In 1.4, there was supposed > to be changes in the GWT framework to make spring integration easier, > and demonstration code somewhere to illustrate this - but I don't seem > to be able to find either. Am I just misunderstanding Issue 389? > > Thanks for any pointers. > > Allen > > > > -- Si l'ignorance peut servir de consolation, elle n'en est pas moins illusoire. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
