When messages are send or dispatched based on recent changes in MULE-3318 and e.g. routing exceptions occur, they are swallowed in TransactionTemplate.execute() return code and a null value is returned instead. Before MULE-3318 these exceptions were handled by subsequent code instead. This now leads to misinterpretation when some routers, e.g. EndpointSelector throws an exception and ExceptionBasedRouter receives a null value instead of the expected exception during its send. An immediate fallout can be seen in current failures of concrete implementations of AbstractXmlPropertyExtractorTestCase.