...
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
...
...
component
...
in
...
that
...
...
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.
...
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 |
---|
Tx. !camel-direct-vm.png|border=1,width=700px! h3. URI format {code} direct-vm:someName {code} Where *someName* can be any string to uniquely identify the endpoint h3. Options {div:class=confluenceTableSmall} || Name || Default Value || Description || | {{block}} | {{false}} | *Camel |
Where someName can be any string to uniquely identify the endpoint
Options
Div | ||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||
|
Samples
In the route below we use the direct component to link the two routes together:
Code Block | ||||
---|---|---|---|---|
| ||||
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-vm:processOrder"); {code} |
And
...
now
...
in
...
another
...
CamelContext,
...
such
...
as
...
another
...
OSGi
...
bundle
Code Block | ||||
---|---|---|---|---|
| ||||
{code:java} from("direct-vm:processOrder") .to("bean:orderService?method=process") .to("activemq:queue:order.out"); {code} |
And
...
the
...
sample
...
using
...
spring
...
DSL:
Code Block | ||||
---|---|---|---|---|
| ||||
{code:xml} <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> {code} {include:Endpoint See Also} - [Direct] - [SEDA] - [VM] |
Include Page | ||||
---|---|---|---|---|
|