[CONF] Apache Camel > Direct-VM

[confluence]

Direct-VM Page added by Claus Ibsen Direct VM Component Available as of Camel 2.10 The direct-vm: component provides direct, synchronous invocation of any consumers in the JVM when a producer sends a message exchange. This endpoint can be used to connect existing routes in the same camel context, as well from other camel contexts in the same JVM. This component differs from the Direct component in that Direct-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 system/boot classpath). At runtime you can swap in new consumers, by stopping the existing consumer(s) and start new consumers. But at any given time there can be at most only one active consumer for a given endpoint URI format direct-vm:someName Where someName can be any string to uniquely identify the endpoint 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-vm:processOrder"); And now in another CamelContext, such as another OSGi bundle from("direct-vm: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-vm:processOrder"/> </route> <route> <from uri="direct-vm:processOrder"/> <to uri="bean:orderService?method=process"/> <to uri="activemq:queue:order.out"/> </route> See Also Configuring Camel Component Endpoint Getting Started Direct SEDA VM Change Notification Preferences View Online | Add Comment