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
VM is an extension to the Seda component.
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:
In the route below we send exchanges across CamelContext instances to a VM queue named
And then we receive exchanges in some other Camel context (such as deployed in another