Wednesday, June 02, 2010

Catch the error raised by your bounded Taskflow

We have scenarios where we consume other third party bounded taskflows.It depends, how well a developer has designed the bounded taskflow.If he has not included an Exception Handler activity in his bounded Taskflow, then for any unhandled exception, the consumer ADF/JSF page blows off.

Best practice is to include an Exception Handler activity in the Bounded taskflow.

Here is a piece of code that can be used to show the errors raised by the Taskflow.This should be kept in your Exception activity's view jsff.

  <af:message id="m1"
message="Error is--->#{controllerContext.currentViewPort.exceptionData.message}" messageType="error"
rendered="#{controllerContext.currentViewPort.exceptionPresent}"/>

No comments: