We have a number of routes: from(HTTP POST).to(JMS) from(JMS).to(SOAP Endpoint).to(JMS) from(JMS).to(MongoDB) from(MongoDB).to(JMS)
Hugely simplified and these are across various JAR services. Are transactions actually useful in the above? Actually understanding the behaviour of code routes is one challenge, understanding with transactional management adds some cognitive overhead which may not be necessary. I'm unsure given the use-cases we have whether it is usual to drop them in favour of client-acking of JMS messages for instance. Thanks, James
