Hi Lucas,
This is correct. Here is a unit test part of the camel project where you
can see that we support 2 options (using @Produce annotation or @Inject
@Uri)
https://github.com/apache/camel/blob/master/components/camel-cdi/src/test/java/org/apache/camel/cdi/ProduceInjectTest.java
https://githu
I'm using the camel-cdi component to inject ProducerTemplates into my EJB's
e.g.
@Inject
@Uri("jms:ToolQueue?preserveMessageQos=true")
ProducerTemplate toolQueueMessageProducer;
My understanding is that the camel-cdi component should manage the look up
and lifecycle of the producer te
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 iss
