For starters, deferred binding is used for creating Javascript files for use on the client side and Spring DI is used on the server side for injecting Java dependencies. Two completely different niches.
Further, in GWT deferred binding is used to control permutations such as localities and user agents. This way a different implementation of a given browser dependent class can be implemented for each browser permutation of JS code compiled. However, the permutation logic is defined in the module gwt.xml files, while in Spring DI annotations are typically used in the consuming classes. You could spend all day going over the differences, but the key take away is one is used for client side code generation to static JS files while the other is used for server side dynamic injection at runtime. If you are looking for JS client side DI for GWT, check out GIN<http://code.google.com/p/google-gin/> . Sincerely, Joseph -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/fkZM57IQAboJ. 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.
