I'm using Google GIN on our current project and it's working out _very_ well. It's really slick and worked out of the box (aside from some minor issues which are resolved quickly by the devs).
-- Arthur Kalmenson On Fri, Feb 27, 2009 at 2:45 PM, Thomas Broyer <[email protected]> wrote: > > > > On 27 fév, 17:41, jesty <[email protected]> wrote: >> I'm starting a new project based on GWT and I want dependency >> injection! >> I've seen this two framework, but I'm not sure about the best choose. >> >> Can you help me? What do you guide me to this choose? > > I'd go for GIN, which has "little-to-no runtime overhead compared to > manual DI" thanks to "using GWT's compile-time Generator support". > http://code.google.com/p/google-gin/ > > But you might also want to look at Suco: > http://code.google.com/p/suco/ > It has a "Guice-like API" but does everything at run-time (contrary to > GIN which tries to do everything at compile-time) > > rocket-gwt and gwtoolbox have the same compile-time approach as GIN > but using a Spring-like XML-based configuration. Given that you get > bean instances by name, I suspect it has a slight overhead over GIN. > However, rocket-gwt supports AOP (interceptors/advices) which others > don't, but again you'll pay it in the compiled code (GIN's plan is to > inline aspects to reduce overhead, and that's probably why it's not > implemented yet...) > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
