Java – Difference between Handler, Manager and Controller

In order for a class to be instantiated it has to be loaded by the classloader...in many cases this is the first time the class has been just-in-time compiled. If you access a static variable on a class, it has to be loaded. If you want to reflect on a class it has to be loaded. There are many circumstances where you might just load a class rather than instantiate.

Also the static initializer(s) for a class fire the first time the class is loaded (and before anything else). If you have an explicit static intializer you can use it to perform a global initialization if need be.

What?

No.

You could use method overloading, something like

public void handle(FunnyException e) {
    ...
}

public void handle(NastyException e) {
    ...
}

, and when calling handle, the most appropriate method will be called. : However, I would say that you basically do three things with Exceptions:

1. Propagate them using throws
2. Propagate them wrapping them in another kind of Exception
3. Catch them and do something about them

1 and 2 are not worth it; calling a generic exception handler would be more verbose than just writing the code required.

3 tends to be longer code, however, it is very unusual that you can catch and treat exceptions in the same way in different parts of your code; if you do, this tends to be a code smell; perhaps you need a broader try statement or some disjoint code needs to be brought together.

So I don't think there's a reason to do what you describe.