title: Is Java's exception handling mechanism an example of the Chain of Responsibility design pattern?
body: <p>I have been reading about the <strong><em>Chain of Responsibility</em></strong> design pattern which basically allows a decoupling between the sender of a request and receiver of the request. The request can be passed along a chain until someone is ready to consume the request. Now in Java when we specify that a method is capable of throwing an <code>Exception</code>  we let the caller of the method handle the exception. If it is not interested it can further propagate the exception up the chain. So can this process be cited as an application of the <strong><em>Chain of Responsibility</em></strong> design pattern?</p>