The direct: component provides direct, synchronous invocation of any consumers when a producer sends a message exchange. This endpoint can be used to connect existing routes in the same camel context.
![]() | Note |
|---|---|
The Seda component provides asynchronous invocation of any consumers when a producer sends a message exchange. |
![]() | Note |
|---|---|
The VM component provides connections between Camel contexts as long they run in the same JVM. |
direct:someName[?options]
Where someName can be any string to uniquely identify the endpoint
| Name | Default Value | Description |
|---|
You can append query options to the URI in the following format,
?option=value&option=value&...
In the route below we use the direct component to link the two routes together:
from("activemq:queue:order.in").to("bean:orderServer?method=validate").to("direct:processOrder");
from("direct:processOrder").to("bean:orderService?method=process").to("activemq:queue:order.out");And the sample using spring DSL:
<route>
<from uri="activemq:queue:order.in"/>
<to uri="bean:orderService?method=validate"/>
<to uri="direct:processOrder"/>
</route>
<route>
<from uri="direct:processOrder"/>
<to uri="bean:orderService?method=process"/>
<to uri="activemq:queue:order.out"/>
</route> See also samples from the SEDA component, how they can be used together.






![[Note]](imagesdb/note.gif)

