public class RethrowErrorHandlerFactory extends LoggingErrorHandlerFactory
Extension to the logging error handler factory that create error handlers that re-throw the original exception. If the exception is an instance of RuntimeException it is re-thrown as is, otherwise it is wrapped inside a new RuntimeException. This factory is it's own error handler and the implementation is thread-safe.
- Last modified
- $Date: 2014-04-09 14:21:20 +0200 (on, 09 apr 2014) $
logprivate static final org.slf4j.Logger log
getErrorHandlerDescription copied from interface:
ErrorHandlerFactoryGet an error handler for the current context. This method is called once for each request/use of an extension point. Errors that happen when processing things related to this extension point will be directed to the error handler returned by this method. The factory may create a new or it may re-use the same error handler for each request. If the error handler is re-used it must be thread-safe.
handleErrorpublic void handleError(InvokationContext<? extends Action> context, Action action, String message, Throwable t)Description copied from interface:
ErrorHandlerHandle an exception that has happened. It is up to the error handler what should happen next. Typically, error should always be logged but the error handler may choose to re-throw the exception. If the exception isn't already a runtime exception it must be wrapped.
Note that there are three stages in the extension mechanism, which may cause some of the parameters to be null:
- Extension point intialization: Eg. when the render factory is being prepared (context and action are both null)
- Extension intialization: Eg. when the action factory is being prepared (action is null)
- Extension rendering: Eg. when rendering the actions of a single extension (context and action are non-null)
- Specified by:
context- The extension context, which can be null
action- The action that was being rendered when the error happened, which can be null
message- An optional error message
t- The error