Hi John,
Thanks for mentioning the point below. > the incoming message if it doesn't match. I.e. if a non-matching .from() is > first to pull the http request, will the http request still be available for > the correct endpoint to process? Asked another way, what does a .from(http) > endpoint do with non-matching http requests? The multiple route option is in production already and from what I have observed in our production system, Camel is clever enough to match an incoming message with the correct route. We have not seen any missing incoming messages. Shing On Tuesday, January 28, 2014 3:17 PM, John Kramer <jakra...@ascenditsolutions.com> wrote: Hello Shing, I'm in somewhat of a similar situation except I'll be pulling messages from multiple email accounts for the from endpoint. I should add that I'm relatively new to camel so please factor that into my responses to follow. My first question regarding the use of the multiple route option is that given the different .from()'s are monitoring the same port is the status of the incoming message if it doesn't match. I.e. if a non-matching .from() is first to pull the http request, will the http request still be available for the correct endpoint to process? Asked another way, what does a .from(http) endpoint do with non-matching http requests? For my situation, there is a great deal of commonality in the needed routing and processing of the incoming messages so I am planning on using a single route. I believe this will result in a camel application that is easier to maintain in the long run. Best, John -- View this message in context: http://camel.465427.n5.nabble.com/Pros-and-cons-of-using-choice-as-opposed-to-having-separate-endpoints-tp5746510p5746552.html Sent from the Camel - Users mailing list archive at Nabble.com.
