Thanks for all the comments and suggestions ! For my case, I will stick with the multi routes option, as it is easier to maintain.
Shing On Tuesday, January 28, 2014 6:55 PM, Claus Ibsen <claus.ib...@gmail.com> wrote: Hi You can also use "dynamic to" with the recipient list like the CXF tomcat example http://camel.apache.org/cxf-tomcat-example.html Then you dont need all the content based router with the when predicates. On Tue, Jan 28, 2014 at 7:10 PM, John Kramer <jakra...@ascenditsolutions.com> wrote: > The hybrid approach seems attractive. > > Assuming your routes are running in the same camel context or jvm, would > using seda or vm be preferred over using jetty? > > E.g.: > > from("jetty:http://localhost:8081/test) > .choice() > .when("...").to("seda:install"l) > .otherwise().to("seda:registration") > > from("seda:install").process(..) > from("seda:registration").process(..) > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Pros-and-cons-of-using-choice-as-opposed-to-having-separate-endpoints-tp5746510p5746562.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen Make your Camel applications look hawt, try: http://hawt.io
