gt;
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/ProducerTemplate-without-using-Spring-tp5739099p5757633.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
--
Charles Moulliard
Apache Committer / Architect @RedHat
Twitter : @cmoulliard | Blog : http://cmoulliard.github.io
ycle of the producer template for me.
Is this correct?
--
View this message in context:
http://camel.465427.n5.nabble.com/ProducerTemplate-without-using-Spring-tp5739099p5757633.html
Sent from the Camel - Users mailing list archive at Nabble.com.
l.com]
Sent: Monday, September 16, 2013 7:25 AM
To: users@camel.apache.org
Subject: Re: ProducerTemplate without using Spring
Hi again,
still looking for a way on how to solve this,
what is the best way of registering a Single ProducerTemplate without using
Spring?
Cause right now I still use th
When you create a CamelContext using new DefaultCamelContext you can
provide a custom registry. For example you can use SimpleRegistry. And
in this registry you can put the producer template, which your
bean/processor can lookup at runtime.
On Wed, Sep 11, 2013 at 10:12 AM, Achim Nierbeck
wrote
Hi again,
still looking for a way on how to solve this,
what is the best way of registering a Single ProducerTemplate without using
Spring?
Cause right now I still use the way of creating a producer Template every
time I need to communicate with
a Camel Route which sooner or later results in a
Hi there,
I have a interesting setup right now using the ProducerTemplate.
I found the following:
http://camel.apache.org/why-does-camel-use-too-many-threads-with-producertemplate.html
on how to add a global usable ProducerTemplate as your not supposed to
recreate the Producer template within eve
