On Thursday, February 28, 2013 6:43:11 PM UTC+1, Marc wrote: > > Hello! > > I just experimented somewhat with Gin and realized that it (v2.0) seems to > break the incremental compilation feature of GWT's development mode, ie. > where I just have to save the .java source file and the gwt dev mode server > automatically incorporates the changes. > > Can someone confirm this or is it my own fault? > I believe you're right. If you "mess" with DI stuff (for example add a new parameter to a constructor annotated with @Inject) the code will break when you reload. You have to rebuild the project at that point. I believe this is due to gin using generators which are not triggered on reload.
> > In general: what DI frameworks are there for GWT? I'd like to have > something akin to Spring's auto-wiring based on interfaces+class path > scanning, but, of course, *before* runtime, ie. at compile time to avoid > performance loss in production. I'm even thinking about an annotation > processor that generates the GinModule bindery code, however, using > something that already exists and is properly maintained is always an > advantage ;-). > I believe gin is the best DI for GWT out there. > Best regards, > Mark > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
