Exceptions declared as inner class.

Question

1) Is it a good idea to declare
exceptions as an inner class, of a root class, from which it is actually
thrown.?
2. So if there are 6 exceptions which are thrown
from the methods of the root class, I will declare 6 inner exception
classes in that root class.
3. Instead of a root class if I have an interface
is it ok to declare these exception classes in the interface?
4. What do you think about this logic?
There are more Exception classes than our actual classes,
so it looks bad, why don't we put all the exception classes
as inner class in one rootException class?

Answer 1

>
If the API user does not catch the exception and
handle it properly then we cannot do much. That isn't what I asked.
I asked if the application code, not the test code, explicitly has a catch block for each exception.
For example if you have the following exceptions.
            class BaseException
            class Exception1 extends BaseException
            class Exception2 extends BaseException
Then that means you have the following code.
              catch(Exception1 e)
                 // Do something with the exception BESIDES logging it
              catch(Exception2 e)
                 // Do something with the exception BESIDES logging it
  Notice in the above that the catch block MUST do something besides just log the exception. Logging doesn't count.
So does your code do this?