On Fri, Mar 19, 2010 at 9:22 AM, Meise, Christoph <[email protected]> wrote: > Interestingly the Direct component is able to span across context. Imagine > you have two spring files with each containing route definitions. All > external interface endpoints ("from:" and the final "to:") are declared in a > third spring file (outside of any camel context). Addinitionally the third > spring file <includes> the route definitions. The two route definitions are > connected via "direct:" endpoints and it works. Is that a bug or a feature? >
Can you show an example? And which server do you use to run it? And what version of Camel are you using? > Regards, > christoph > > -----Ursprüngliche Nachricht----- > Von: Stephen Gargan [mailto:[email protected]] > Gesendet: Donnerstag, 18. März 2010 18:58 > An: [email protected] > Betreff: Re: Synchronous MEP across camel contexts > > Cheap and cheerful, you could use JMS, ActiveMQ is very easy to embed > for this purpose (like a basic NMR). It will give you cross context > blocking you are looking for and also make it easy to separate the > contexts across the network if you have to. > > ste > > On Thu, Mar 18, 2010 at 10:42 AM, Alexandros Karypidis > <[email protected]> wrote: >> Hi, >> >> I would like to perform a synchronous in/out exchange across different camel >> contexts. >> >> I tried using "direct" components but those do not span contexts. The only >> component I've found that does that, is the "vm" component. Unfortunately, >> "vm" does one-way exchanges, so it's not suitable for what I need. >> >> Any ideas how to go about doing this? >> >> Thanks in advance for your help. >> >> > -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
