Thanks, Jeff. Good name by the way:) I guess I should have mentioned that I am aware of the removeHandler method so I guess my question then really boils down to what happens if you don't call it?
For example, suppose composite a has a reference to composite b and b calls addHandler for events that composite a will fire. Some user action then causes composite a to create a new instance of composite b overriding its original reference to the 1st instance of b that it created. What should happen when composite a fires off the events that composite b handles? The 1st instance of composite b might already have been garbage collected but the EvenHandler still has references to the handlers it created. The reason I am asking is because I've never seen an exception thrown in these cases either in dev or in production. Is the event handler smart enough to know that a handler is dead and should not be called even though removeHandler was never called for it? Jeff On Mon, Dec 20, 2010 at 4:34 PM, Jeff Larsen <larse...@gmail.com> wrote: > addHandler returns an interface HandlerRegistration. > > you'll notice a method in there removeHandler(). Call that and it will > destroy the event from the event bus. > > -- > 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-tool...@googlegroups.com. > To unsubscribe from this group, send email to > google-web-toolkit+unsubscr...@googlegroups.com<google-web-toolkit%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > -- *Jeff Schwartz* -- 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-tool...@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.
