Details
-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
7.21.0.Final
-
None
-
NEW
-
NEW
Description
Error and Escalation event subprocess are usualy linked to specific Code defined in bpmn2 cuasing the start only if Code matches.
Errors can be defined without Code and in this case the subprocess should start even without exception match.
But if a runtime exception occurs (this should be matched only by specific Error Code or Null Error Code) , it causes a Escalation Event Subprocess to Start
Something wrong is in the file ProcessHandler.java:
if (faultCode != null)
{ String trimmedType = type.replaceFirst(replaceRegExp, ""); exceptionScope.setExceptionHandler(trimmedType, exceptionHandler); eventSubProcessHandlers.add(trimmedType); }else
{ exceptionScope.setExceptionHandler(faultCode, exceptionHandler); }If the faultCode is null (and is always null in case of Escalation) , the escalation start event is linked to "null" exception handler, and cause the buggy behaviour at runtime