Friday, March 13, 2015

UndeclaredThrowableException

java.lang.reflect.UndeclaredThrowableException

UndeclaredThrowableException is described in the javadoc comments as:

Thrown by a method invocation on a proxy instance if its invocation handler's {link: InvocationHandler#invoke invoke} method throws a checked exception (a Throwable that is not assignable to RuntimeException or Error) that is not assignable to any of the exception types declared in the throws clause of the method that was invoked on the proxy instance and dispatched to the invocation handler.

An UndeclaredThrowableException instance contains the undeclared checked exception that was thrown by the invocation handler, and it can be retrieved with the getUndeclaredThrowable() method. UndeclaredThrowableException extends RuntimeException, so it is an unchecked exception that wraps a checked exception.

As of release 1.4, this exception has been retrofitted to conform to the general purpose exception-chaining mechanism. The 'undeclared checked exception that was thrown by the invocation handler' that may be provided at construction time and accessed via the {link: #getUndeclaredThrowable()} method is now known as the cause, and may be accessed via the {@link Throwable#getCause()} method, as well as the aforementioned 'legacy method.'
author: Peter Jones version: 1.13, 04/02/19 see: InvocationHandler since: JDK1.3

Where is this exception thrown?

Following, is a list of exception messages cross-referenced to the source code responsible for throwing them. Click on the method link to view the code and see how the exception is thrown.

  • UndeclaredThrowableException is not thrown within any available source code.

How is this exception thrown?

The following sub-sections identify where this exception is thrown, and how (or why) the code is throwing the exception.

Any source code quoted in this section is subject to the Java Research License unless stated otherwise.

  • UndeclaredThrowableException is not thrown within the available source code.

No comments:

Post a Comment