Handling Business Process Choreographer EJB API exceptions
If a method in the BusinessFlowManagerService interface or the
HumanTaskManagerService interface does not complete successfully, an exception
is thrown that denotes the cause of the error. You can handle this exception
specifically to provide guidance to the caller.
About this task
However, it is common practice to handle only a subset of the
exceptions specifically and to provide general guidance for the other potential
exceptions. All specific exceptions inherit from a generic ProcessException
or TaskException. Catch generic exceptions with a final catch(ProcessException) or catch(TaskException) statement.
This statement helps to ensure the upward compatibility of your application
program because it takes account of all of the other exceptions that can occur.
This topic only applies to BAW, and is located in the BAW repository. Last updated on 2025-03-13 12:15