There are two different ways to send messages to any Camel Endpoint from a POJO
@EndpointInject
To allow sending of messages from POJOs you can use the @EndpointInject() annotation. This will inject either a ProducerTemplate or CamelTemplate so that the bean can send participate in message exchanges.
e.g. lets Example: send a message to the foo.bar
ActiveMQ queue in ActiveMQ at some point:
Code Block | ||||
---|---|---|---|---|
| ||||
public class Foo {
@EndpointInject(uri="activemq:foo.bar")
ProducerTemplate producer;
public void doSomething() {
if (whatever) {
producer.sendBody("<hello>world!</hello>");
}
}
}
|
The downside of this is that your code is now dependent on a Camel API, the ProducerTemplate
. The next section describes how to remove this dependency.
Tip |
---|
See POJO Consuming for how to use a property on the bean as endpoint configuration, e.g., using the |
Hiding the Camel APIs From Your Code Using @Produce
We recommend Hiding Middleware APIs from your application code so the next option might be more suitable.
@Produce
You can add the the @Produce
annotation to an injection point (a field or property setter) using a ProducerTemplate
or using some interface you use in your business logic. e.g.Example:
Code Block | ||||
---|---|---|---|---|
| ||||
public interface MyListener {
String sayHello(String name);
}
public class MyBean {
@Produce(uri = "activemq:foo")
protected MyListener producer;
public void doSomething() {
// lets send a message
String response = producer.sayHello("James");
}
}
|
Here we have an injected Camel will automatically inject a smart client side proxy , the at the @Produce
annotation - an instance of the MyListener
instance. When we invoke methods on this interface the method call is turned into an object and using the Camel Spring Remoting mechanism it is sent to the endpoint - in this case the ActiveMQ endpoint to queue foo
; then the caller blocks for a response.
...