Is “throws Exception” bad practice?

Question

I\'m reviewing code for a colleague and I encounter a piece of code similar to this:

public X Foo1(Y y) throws Exception {
    X result = new X(y);
    resul         


        

Answer 1

This forces everybody using this method to handle thrown Exceptions.

Even if you like using checked exceptions (which I don't) this leaves you with no information at all what kind of stuff might go wrong. So you can't really handle it in a meaningful way.