|@MessageDriven is @deprecated|
@MessageDriven is deprecated in Camel 1.x. You should use @Consume instead. Its removed in Camel 2.0.
To consume a message you use either the @MessageDriven annotation or from 1.5.0 the @Consume annotation to mark a particular method of a bean as being a consumer method. The uri of the annotation defines the Camel Endpoint to consume from.
e.g. lets invoke the onCheese() method with the String body of the inbound JMS message from ActiveMQ on the cheese queue; this will use the Type Converter to convert the JMS ObjectMessage or BytesMessage to a String - or just use a TextMessage from JMS
What this does is basically create a route that looks kinda like this
|When using more than one CamelContext|
When you use more than 1 CamelContext you might end up with each of them creating a POJO Consuming.
Available as of Camel 2.0
See the warning above.
You can use the context option to specify which CamelContext the consumer should only apply for. For example:
The consumer above will only be created for the CamelContext that have the context id = camel-1. You set this id in the XML tag:
If you want to invoke a bean method from many different endpoints or within different complex routes in different circumstances you can just use the normal routing DSL or the Spring XML configuration file.
which will then look up in the Registry and find the bean and invoke the given bean name. (You can omit the method name and have Camel figure out the right method based on the method annotations and body type).
You can always use the bean endpoint
Using the @MessageDriven/@Consume annotations are simpler when you are creating a simple route with a single well defined input URI.
However if you require more complex routes or the same bean method needs to be invoked from many places then please use the routing DSL as shown above.