> > i just eliminated all "old"(and changed where necessary) imports and put > "com.google.gwt.event.shared.EventBus" in each startMethod. > but i have some bad feelings about that >
Why? Isn't this the normal situation? Every Activity/Places related class can take the new web.bindery EventBus, *except* Activity.start(AcceptsOneWidget view, EventBus eventBus). But this method is only called by the ActivityManager and this class will provide an old EventBus (an old ResettableEventBus that takes your global new web.bindery EventBus as a constructor parameter) to make things work. > - some tests call the start methods. at the moment start(panel, new > com.google.gwt.event.shared.SimpleEventBus()) works (because i know that > the methods don't use the event bus - all are using the eventBus injected > on construction-time) - but this could fail. so either i use only the "old" > eventBus in Tests (where possible) or wrap it like the managers do in a > resttableEventBus? > I would always use the new web.bindery EventBus and if needed wrap it in an old Resettable/CountingEventBus. Why do you inject an EventBus in your Activity's constructor although you get one via the Activity.start() method? You should use the one provided by the start() method, as all handlers are automatically removed once the activity stops. But maybe I misunderstood you. -- 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/-/TBeqo3tlDDoJ. 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.
