Logged a ticket to allow turn off event notifier in the producer template
https://issues.apache.org/jira/browse/CAMEL-6628

On Mon, Aug 12, 2013 at 3:55 PM, pmcb55 <mcbenne...@dnb.com> wrote:
> Well actually, our production code makes extensive use of the
> ProducerTemplate to make explicit calls from our application server code
> (which just supports a standard web application) to simple Camel routes that
> invoke on backend services that all expose HTTP endpoints (so of course we
> use the HTTP4 component in those routes a lot).
>
> So the example I gave above is actually very close to what we are currently
> doing in our Production system. In fact, this slightly simplified route is
> extremely close to what we have in Production today:
>
>       from("direct://GET_BEST_REPORT_FROM_THOSE_CURRENTLY_AVAILABLE")
>
> .enrich("http4://www.example.com/backend_services/GET_ALL_AVAILABLE_REPORTS",
> new MyAggregator())
>
> .enrich("http4://www.example.com/backend_services/PICK_BEST_REPORT", new
> MyAggregator())
>          .enrich("http4://www.example.com/backend_services/GO_GET_REPORT",
> new MyAggregator());
>
> That's the kind of simple Camel route we invoke (using
> '*producer.send("direct://GET_BEST_REPORT_FROM_THOSE_CURRENTLY_AVAILABLE",
> exchangeWithUserSpecifiedDataFromWebForm);*') from our web request
> processing code all the time! This has been working perfectly for a long
> time, and all I want to do now is gather timing stats for those PRODUCTION
> Camel routes :)
>
> (And as I said before, I know I could go to JMX, but the sample code I
> showed in my original post is so simple, and so intuitive (and so very
> nearly works perfectly!), that I'd love to just get it working for this
> simple use case.)
>
> Cheers,
>
> Pat.
>
>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/Bug-with-addEventNotifier-fires-two-exchange-sent-events-for-each-Exchange-sent-tp5737086p5737150.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

Reply via email to