Page History

{tip}

{tip:title=Connection to other camel contexts}
The [VM] component provides connections between Camel contexts as long they run in the same *JVM*.
{tip}

h3. URI format

{code}
direct:someName[?options]
{code

}

Where *someName* can be any string to uniquely identify the endpoint

h3. Options
{div:class=confluenceTableSmall}
|| Name || Default Value || Description ||
| {{allowMultipleConsumers}} | {{true}} | *@deprecated* If set to {{false}}, then when a second consumer is started on the endpoint, an {{IllegalStateException}} is thrown. *Will be removed in Camel 2.1:* Direct endpoint does not support multiple consumers. |
| {{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. |
{div}

}}

h3. Samples
In the route below we use the direct component to link the two routes together:

{code:java}
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");
{code}

{code:xml}
   <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>    
{code}