Great !! Thanks a lot for explaining this in detail. My bad. For some reason I felt that the route is not complete and that the compiler would complain without a "to". I removed that "to" now and this is exactly what I need.
Thank a lot to everybody else for taking the time to make this clear. Though this is my first project with Camel, I am loving it a lot. Now, the community is one more reason. Cheers, Arun Manivannan On Friday, 4 October, 2013 at 12:44 PM, kraythe [via Camel] wrote: > The aggregated exchange is the one that gets returned and how the > aggregated exchange is created depends on the aggregation strategy you use. > When a route stops either by calling stop or merely not routing anymore, > the exchange on the last part of the route could be considered a reply. In > most cases it will reply back to the caller (unless you set a reply-to > destination in a JMS based route or some other cases). In your case if all > you want to do is return the enriched exchange then you dont need any to() > call. Just stop after the marshal. > > *Robert Simmons Jr. MSc. - Lead Java Architect @ EA* > *Author of: Hardcore Java (2003) and Maintainable Java (2012)* > *LinkedIn: **http://www.linkedin.com/pub/robert-simmons/40/852/a39* > > > On Wed, Oct 2, 2013 at 1:21 PM, arunodhaya80 <[hidden email] > (/user/SendEmail.jtp?type=node&node=5740851&i=0)> wrote: > > > Apologies for not making myself clear enough. > > > > As you could see, I am using Camel to route the request to a REST service > > to > > two bean methods. These bean methods enrich a single Entity through the > > AggregationStrategy configured in the multicast. > > > > My understanding is that the last exchange returned by the > > AggregationStrategy is the one which gets returned to the user via the REST > > response. Is it correct? > > > > That being the case, I am not using the `to` at all. Am I using the `to` > > to > > just to satisfy the compiler. I don't, in fact, need to log the output. > > > > > > > > -- > > View this message in context: > > http://camel.465427.n5.nabble.com/Apache-Camel-Multicast-Is-there-a-null-or-a-similar-endpoint-tp5740664p5740780.html > > Sent from the Camel - Users mailing list archive at Nabble.com > > (http://Nabble.com). > > > > > If you reply to this email, your message will be added to the discussion > below: > http://camel.465427.n5.nabble.com/Apache-Camel-Multicast-Is-there-a-null-or-a-similar-endpoint-tp5740664p5740851.html > > To unsubscribe from Apache Camel - Multicast - Is there a 'null' or a similar > endpoint ?, click here > (http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5740664&code=dGVjaEBhcnVubWEuY29tfDU3NDA2NjR8LTEzNjIxMTkxNjc=). > NAML > (http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml) > -- View this message in context: http://camel.465427.n5.nabble.com/Apache-Camel-Multicast-Is-there-a-null-or-a-similar-endpoint-tp5740664p5740854.html Sent from the Camel - Users mailing list archive at Nabble.com.
