camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Odom <>
Subject Re: Can Camel VM be used in Karaf cross contexts in different bundles?
Date Tue, 03 Nov 2015 19:38:39 GMT
Take a look at direct-vm


*Chris Odom | Sr Consultant | Media Driver*
512.799.0270 |
810 Hester's Crossing, Suite 165, Round Rock, TX 78681

On Tue, Nov 3, 2015 at 12:40 PM, bocamel <> wrote:

> I am running a few bundles in Karaf, each has its own Camel context.  I
> tried
> to use VM to communicate between them, i.e. one bundle (B1) is a producer
> to
> a VM endpoint, and another (B2) is the consumer of the VM endpoint.  In the
> Camel route in B2, the route first tests a properties value in a <choice>.
> I received an error saying that the property was not defined (even though
> it
> is defined in B2).  After I repeated its definition in B1 as well, that
> error went away.  Now it complains that some of the bean
> injected/referenced
> in the vm route is not defined (though it is defined in B2's
> camel-context.xml).
> So my question is, when using vm across Camel contexts, do we have to
> define
> all the properties, beans (that are used by the consumer) on the producer
> side as well?  I am running this in Karaf 4.0.2, with Camel 2.15.2.  Any
> insight would be greatly appreciated.
> --
> View this message in context:
> Sent from the Camel - Users mailing list archive at

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message