No... It is usually considered bad form.

But what kind of Error do you plan to catch this way?

If it's only to catch NoClassDefFoundError, then not only it won't
work all the time and moreover there's a better alternative, clearly
explained in Joshua Bloch and Neal Gafter's
"Java Puzzlers" book.  Puzzle 44: "Cutting Class".

A small excerpt:

"In summary, *do not depend on catching NoClassDefFoundError.
"The language specification carefully describes when class
"initialization occurs [JLS 12.4.1], but class loading is far less
"predictable. More generally, *it is rarely appropriate to catch
"Error or its subclasses*. These exceptions are reserved for
"failures from which recovery is not feasible.

A NoClassDefFoundError can be worked around by using
reflection and catching a ClassNotFoundException (which, as
it names implies, is not an Error).

So remember that catching Throwable will not even catch
all NoClassDefFoundError.

That said I still sometimes "catch" Throwable using:

       Thread.setDefaultUncaughtExceptionHandler(
           new Thread.UncaughtExceptionHandler() {
               public void uncaughtException(
                   final Thread t, final Throwable e) {

to do some special kind of logging should "the sh.t hit the fan"
(eg when a 3rd party API which we're forced to use exhibits
some strange behaviour :)

Hope it helps a little bit,

 Alex