While many of our processes are triggered by some external event (timer, file transfers, emails, web/REST/SOAP requests), there are a number of instances where we want to trigger a route from within our code. I'm trying to understand how Camel allows me to do this and what the recommended practices/patterns for this type of interaction are.
I see a handful of components which seem like they would meet the criteria for trigger, but I'm not clear on which I should use. Basically I'm looking at: * direct * jms * seda * vm It seems to me like they are similar, but it is unclear which are best under what conditions. Is there some document comparing the pros and cons and potential use cases for these transports in non-test circumstances? And is the general pattern of direct triggering to use a ProducerTemplate? It felt a bit like this was mainly for testing, but I don't see other methods used in the examples (or for that matter, I don't recall seeing ProducerTemplate in non-test code, though I haven't searched too closely). Basically, just trying to get some guidance as to the recommended practice. Thanks. --Tim -- View this message in context: http://old.nabble.com/Best-Practices-for-Triggering-Routes-from-Code-tp26617252p26617252.html Sent from the Camel - Users mailing list archive at Nabble.com.
