XMLConfigurator.createClassInstance() should catch Throwable ?

[Tom Zeller]

> If there's a specific case we've actually encountered then I
> guess that's a good argument - for better logging, etc.  But there's
> probably umpteen other similar cases we don't (yet).

Yes, I think I had the same/similar thought.

I guess because this particular use/error-case is in a "core" package
and involves a classloader it seems worth the effort to catch/handle
Throwable to help troubleshoot classpath issues.

But I agree, we could certainly just doc this one and move on.

Tom