[ODE-59] Runtime exceptions should bubble up

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 1.0-incubating
• Fix Version/s: 1.0-incubating
• Component/s: BPEL Runtime
• Assignee: Matthieu Riou
• Reporter: Matthieu Riou
• Created: 03/Oct/06 22:03
• Updated: 29/May/07 22:05
• Resolved: 07/Nov/06 23:40

Description

Curremtly in the ASSIGN there's the following code:

try

{ copy(aCopy); }

catch (FaultException fault)

{ faultData = createFault(fault.getQName(), aCopy, fault .getMessage()); break; }

catch (Exception ex)

{ __log.fatal("Unexpected exception in assignment, terminating process", ex); instance(ASSIGN.this); getBpelRuntimeContext().terminate(); break; }

Which practically means that any non-fault exception will result in the process terminating. However an engine failure (a sneaky NPE hidden in a rarely executed piece of code) shouldn't affect the process. So such an exception should bubble up to the IL and trigger a transaction rollback.