Hi P.G. I've seen a lot of ways to achieve that integration, and none looks complicated. The fact is that spring-gwt integration is easy (thanks to R. Jellinghaus' refactoring of the RemoteServiceServlet), which explains the plethora of libraries. Hibernate-gwt integration on the other hand is hard, that's why there are only 3 (afaik) out there of which only 1 (imo) is to be taken seriously. I guess it all comes down to :
- what kind of flavour you prefer - if you like annotations or XML - prefer convention over configuration - whether you can live with a certain 3rd party dependency or not - how much documentation you need - how big and active the supporting community is Especially the later point is a threshold for commercial adoption when arguing in favour of a library in technical meetings, so maybe that's the answer you are looking for ;-) On Aug 11, 11:04 am, "P.G.Taboada" <pgtabo...@googlemail.com> wrote: > Hi, > > I have seen a lot of (quite complicated) Spring and GWT integration > approaches, and I wonder why noone is using the autowiring bean bean > factory to simple auto-inject the required beans into the GWT RPC > services. > > http://pgt.de/2009/07/17/non-invasive-gwt-and-spring-integration-relo... > > I have been using this approach for a while. It is easy to setup and > works perfectly. > > Would appreciate any comments. --~--~---------~--~----~------------~-------~--~----~ 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-Toolkit@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 -~----------~----~----~----~------~----~------~--~---
