Details
-
Bug
-
Resolution: Done
-
Major
-
jBPM 6.2.0.CR3
-
None
Description
BPMN2 spec tells that If errorCode is not set, catch all errors (= It becomes a default exception handler).
Table 8.41 – Error attributes and model associations
structureRef : ItemDefinition [0..1] | An ItemDefinition is used to define the “payload” of the Error.
name : string | The descriptive name of the Error.
errorCode: string | For an End Event:
If the result is an Error, then the errorCode MUST be supplied (if the processType attribute of the Process is set to execut-able) This “throws” the Error.
For an Intermediate Event within normal flow:
If the trigger is an Error, then the errorCode MUST be entered (if the processType attribute of the Process is set to execut-
able). This “throws” the Error.
For an Intermediate Event attached to the boundary of an Activity:
If the trigger is an Error, then the errorCode MAY be entered. This Event “catches” the Error. If there is no errorCode, then any error SHALL trigger the Event. If there is an errorCode, then only an Error that matches the errorCode SHALL trigger the Event.
But current jBPM implementation doesn't register the default ('null' key) exception handler when errorCode doesn't exist.
