Error Handler builder inputsAdded by IBM on August 31, 2010 | Version 1 (Original)
|This topic describes the inputs for the Error Handler builder.
This topic describes the inputs for the Error Handler builder.
- General Inputs
- Post-Handler Processing
|Name||Enter a name for this builder call. The WebSphere® Portlet Factory Designer displays this name in the builder call list.|
|Exceptions ||Select an error catching mode. You can choose: |
Catch exceptions thrown by a specific action
Select this radio button to catch an exception related to a specific model action. Specify the action in the Try Action input.Catch all unhandled exceptions
Select this radio button to catch all unhandled exception in a model. Any exception that is not explicitly handled by another Error Handler builder is caught and handled.
|Try Action||This input is available when you select Catch exceptions thrown by a specific action in the Exceptions input. |
Specify the action in which you want to have your error handler method called during an exception. The error handling can be specified on any action, such as a page, method, or action list.
Select main as the action to handle all methods in a model that are not explicitly handled elsewhere.
|Catch Action||Enter an action to be called as a result of the exception. This action can be any action, such as a page, method, or action list item. |
|Exception Class||To focus the error handler on a particular type of exception, enter the fully-qualified class name here. For example, if you wanted this error handler to process File Not Found exceptions, you would enter: java.io.FileNotFoundException. |
If any other exception occurs, the default error handler processes it.
|Allow Nested Handlers||If the handler action specified by this Error Handler builder call (the Catch Action input) directly or indirectly throws an exception and Catch All Unhandled Exceptions in the Exceptions input is specified, the same error handler is re-invoked to handle this second exception. Because allowing handlers for handlers can lead to unbounded recursion, ensure that unbounded recursion cannot happen in your model. You can do this in the following ways.
Select one of the following options.
- Code your error handlers so exceptions are impossible.
- Set the Allow Nested Handlers input to No.
No: nested exception will invoke default JSP
Set to prevent recursion. Yes: call error handler if handler throws exception
Set to let handler action be re-invoked.
When the error handler finishes, you can either continue or bypass subsequent model actions.
|Post-Handler Processing||Select one of the following options.|
No further actions after handler runs
Terminates the current request. Continue request processing
Continues application processing.
Parent topic: Error Handler builder: wpf7