Fair point, Ben. The onSuccess() method is where we are creating the async objects and no other code *should* be interacting with those objects elsewhere. However, other objects that needed to exist on page load, long before async code gets loaded, do need to interact with objects that are created asynchronously (but only once they have actually been created). So those objects can't attempt interacting with those objects if they are null. So it is indeed a developer's bug to not be checking for null.
The issue here is that in dev mode you won't catch those bugs and when you encounter them in production mode you can't easily determine where the code is breaking. Does that make sense? -- 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.
