...
This component allows also to connect routes deployed in different OSGI Bundles as you can see here after. Even if they are running in different bundles, the camel routes will use
the same thread. That autorises to develop applications using Transactions - Tx.
URI format
| Code Block |
|---|
direct-vm:someName
|
Where someName can be any string to uniquely identify the endpoint
...
| Div |
|---|
| class | confluenceTableSmall |
|---|
|
Name | Default Value | Description |
|---|
block
| false
| Camel 2.11.1: If sending a message to a direct endpoint which has no active consumer, then we can tell the producer to block and wait for the consumer to become active. | timeout
| 30000
| Camel 2.11.1: The timeout value to use if block is enabled. | failIfNoConsumers
| true | Camel 2.16.0: Indicates whether the producer should fail by throwing an exception when sending to a DIRECT-VM endpoint with no active consumers. |
|
Samples
In the route below we use the direct component to link the two routes together:
| Code Block |
|---|
|
from("activemq:queue:order.in")
.to("bean:orderServer?method=validate")
.to("direct-vm:processOrder");
|
And now in another CamelContext, such as another OSGi bundle
| Code Block |
|---|
|
from("direct-vm:processOrder")
.to("bean:orderService?method=process")
.to("activemq:queue:order.out");
|
And the sample using spring DSL:
| Code Block |
|---|
|
<route>
<from uri="activemq:queue:order.in"/>
<to uri="bean:orderService?method=validate"/>
<to uri="direct-vm:processOrder"/>
</route>
<route>
<from uri="direct-vm:processOrder"/>
<to uri="bean:orderService?method=process"/>
<to uri="activemq:queue:order.out"/>
</route>
|
| Include Page |
|---|
| Endpoint See Also |
|---|
| Endpoint See Also |
|---|
|
