Project: mule
Issue MULE-7620: Define unified way to define the exception handler in execution scopes in mule
Currently exception handler is defined by: - Flow - Transactional scope - Exception strategies - Outbound endpoint (when using LaxAsync) due bug fix. In some places the exception handler is retrieve by doing: event.getFlowConstruct().getExceptionListener() (AsyncInterceptingMessageProcessor). This is bad design because the MuleEvent should not have a reference to the FlowConstruct and the exception handler should not be retrieved from the MuleEvent. The MuleEvent contains dynamic information related to the current message while the exception handler must be defined statically by the flow configuration. The recommendation is that each scope or execution block (new Threads running part of the flow) should have statically defined the exception handler to use.
Story points: 13