Direct Component

Table of Contents

URI format
Options
Samples
See Also

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.

	Tip
	Asynchronous The SEDA component provides asynchronous invocation of any consumers when a producer sends a message exchange.

TIP:*Connection to other camel contexts* The VM component provides connections between Camel contexts as long they run in the same JVM.

URI format

direct:someName[?options]

Where someName can be any string to uniquely identify the endpoint

Options

The Direct component supports 2 options which are listed below.

{% raw %}

Name	Java Type	Description
block	`boolean`	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	`long`	The timeout value to use if block is enabled.

{% endraw %}

The Direct component supports 8 endpoint options which are listed below:

{% raw %}

Name	Group	Default	Java Type	Description
name	common		`String`	Required Name of direct endpoint
bridgeErrorHandler	consumer	`false`	`boolean`	Allows for bridging the consumer to the Camel routing Error Handler which mean any exceptions occurred while the consumer is trying to pickup incoming messages or the likes will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions that will be logged at WARN/ERROR level and ignored.
exceptionHandler	consumer (advanced)		`ExceptionHandler`	To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this options is not in use. By default the consumer will deal with exceptions that will be logged at WARN/ERROR level and ignored.
exchangePattern	consumer (advanced)		`ExchangePattern`	Sets the default exchange pattern when creating an exchange.
block	producer	`false`	`boolean`	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.
failIfNoConsumers	producer	`false`	`boolean`	Whether the producer should fail by throwing an exception when sending to a DIRECT endpoint with no active consumers.
timeout	producer	`30000`	`long`	The timeout value to use if block is enabled.
synchronous	advanced	`false`	`boolean`	Sets whether synchronous processing should be strictly used or Camel is allowed to use asynchronous processing (if supported).

{% endraw %}

Samples

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.