I think the main point of GWT MVP is that the presenters (actions in 2.1) are independent of the implementation of the View, so you can easily share mock views for easy testing.
In addition, itβs normal to have presentations that depend on presentations (= methods of calling the presenter), but not vice versa (well, yes, but through the interface).
I usually just keep the Presenter link inside the View, so that FieldUpdater and inner classes can call methods in Presenter. You can put these methods into an interface, but that doesn't make sense, since there is only one version of this type of Presenter.
Or, if you want things to be more untied, just ask View to send the GWT event that Presenter is listening to.
source share