An idea come to my mind why there is no Exception Context or anything similar .
Why I need this;
many times you have to re catch the same exception and behave in similar behavior or even a little bit different from different locations in your application.
a solution for the re write problem of the same lines of catching and handling is to have something like Exception Context that any thrown exception get register in this context and by the usage of AOP Aspect Oriented Programing you can define which exception handling method should be invoked after which business methods.
Exception Handling methodology that just throw the exception and have just one Exception Handling class that is responsible for handling the thrown exception is not the ultimate methodology for handling all the situations.