The danger is that if you add handlers, and than later in your code call setHandlerManager with a new HandlerManager. If we dont check for a prior existing HandlerManager, all old HandlerRegistration's will be lost. If you dont know what happened, you will search forever why your old handlers are not working.
You wont have the problem with a createHandlerManager method. On 9 Feb., 17:55, Ray Ryan <[email protected]> wrote: > If you're right that swapping HMs midstream is a bad idea, I think you need > a better argument than "it's a bad idea." What's the actual danger? If I'm > making my own HM I'm already pretty savvy. Why tie my hands? > > But yes, if you win that point, I agree with the change to replace setHM(HM) > with HM createHM() -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
