VM Component
The vm: component provides asynchronous SEDA behavior, exchanging messages on a BlockingQueue and invoking consumers in a separate thread pool.
This component differs from the Seda component in that VM supports communication across CamelContext instances - so you can use this mechanism to communicate across web applications (provided that camel-core.jar
is on the system/boot
classpath).
VM is an extension to the Seda component.
URI format
Code Block |
---|
vm:queueName[?options] |
Where queueName
can be any string to uniquely identify the endpoint within the JVM (or at least within the classloader that loaded camel-core.jar)
You can append query options to the URI in the following format: ?option=value&option=value&...
Info | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
An exactly identical VM endpoint URI must be used for both the producer and the consumer endpoint. Otherwise, Camel will create a second VM endpoint despite that the
Notice that we have to use the full URI, including options in both the producer and consumer. In Camel 2.4 this has been fixed so that only the queue name must match. Using the queue name
|
Options
See the Seda component for options and other important usage details as the same rules apply to the Vm component.
Samples
In the route below we send exchanges across CamelContext instances to a VM queue named order.email
:
Code Block | ||||
---|---|---|---|---|
| ||||
from("direct:in").bean(MyOrderBean.class).to("vm:order.email"); |
And then we receive exchanges in some other Camel context (such as deployed in another .war
application):
Code Block | ||||
---|---|---|---|---|
| ||||
from("vm:order.email").bean(MyOrderEmailSender.class); |
Include Page | ||||
---|---|---|---|---|
|