File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes GWT and the fly likes Is HandlerManager really necessary? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Frameworks » GWT
Bookmark "Is HandlerManager really necessary?" Watch "Is HandlerManager really necessary?" New topic

Is HandlerManager really necessary?

Matt Erwin

Joined: May 01, 2012
Posts: 1
Hello everyone,

My partner and I have been writing a web app following the MVP architecture laid out here:

As this is our first foray into web development, GWT has been incredibly helpful and useful, but forgive my questions should they sound naive.

I'm trying to figure out why the HandlerManager is even necessary. The way we currently manage our app through the AppController is to keep a stack of Presenters and push new screens onto the stack and pop them off when you're done with them.

In the Contacts example Google provides in the above link, it seems the HandlerManager does 2 things when the event is called: write a history item, go to a new presenter.

Is this really necessary? If we end up making an app with 100 screens, we'll end up having 100 Event classes and 100 EventHandler classes. Seems to me like the views and presenters should be enough, while each presenter and decide which presenters it can go to.

Thanks in advance to anyone that can either confirm my feelings or give me a reason to use the HandlerManager.

Vandre Caetano

Joined: Dec 19, 2007
Posts: 15
I don't really like the eventHandler either (Or the eventBus)
Could you explain a bit more how you are doing you AppController? it seens like a good idea.

I agree. Here's the link:
subject: Is HandlerManager really necessary?
It's not a secret anymore!