The used AsyncProvider from GIN will be integrated in GWT 2.4 (see: http://code.google.com/p/google-web-toolkit/source/browse/releases/2.4/user/src/com/google/gwt/core/client/AsyncProvider.java). So if you do not depend on GIN you should wait for GWT 2.4. If you can't wait you can try and rewrite the code to use your DI framework or to use GWT.runAsync directly.
As Thomas said your code example is pretty dangerous. In Dev mode GWT.runAsync acts synchronously so it may work during development. But when you compile your app you will return null the first time you request an activity. Just imagine onSuccess will be executed after getActivity() has finished. -- J. -- 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/-/xySMboZIpiEJ. 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.
