This is horrible. Having the exception handler inside the MuleEvent is bad. The MuleEvent doesn't has (or at least shouldn't have) anything to do with the processing context of the message. The MuleEvent should only be a context for the message content and not for the behaviour. At least not for a behaviour that can be change depending on which part of the flow is processing the message.