Hi James, Thank you again for this very fast answer. Indeed I have missed VmRouteTest which is exactly what I was looking for. I'll think about the other solutions performance wise but BlockingQueue from vm component might be the best. Regards, Sébastien.
James.Strachan wrote: > > 2008/10/10 Seb- <[EMAIL PROTECTED]>: >> >> Hi, >> I would like to know if there's a way/workaround to communicate between >> multiple camel contexts. >> ie direct:bleh here: >> >> <!-- START SNIPPET: example2 --> >> <camelContext id="camel1" >> xmlns="http://activemq.apache.org/camel/schema/spring";> >> <route> >> <from uri="file:src/data?noop=true"/> >> <to uri="direct:bleh"/> >> </route> >> </camelContext> >> >> <!-- START SNIPPET: example2 --> >> <camelContext id="camel2" >> xmlns="http://activemq.apache.org/camel/schema/spring";> >> <route> >> <from uri="direct:bleh"/> >> <to uri="file://target/test2?noop=true"/> >> </route> >> </camelContext> > > To communicate between contexts you can use the VM transport > http://activemq.apache.org/camel/vm.html > > (assuming the same classloader is used) > > otherwise other components like ActiveMQ, JMS, JPA, File can be used - > which also work across classloaders, JVMs and machines > http://activemq.apache.org/camel/components.html > > -- > James > ------- > http://macstrac.blogspot.com/ > > Open Source Integration > http://open.iona.com > > -- View this message in context: http://www.nabble.com/Endpoints---Routes-communication-between-multiple-camel-contexts-tp19920500s22882p19921101.html Sent from the Camel - Users mailing list archive at Nabble.com.
