-
1. Re: VM and SEDA
janstey Nov 4, 2009 7:30 AM (in response to sriram_imshriram)Yeah, SEDA only works within a single CamelContext (one file in your case). If you want to use VM do communicate across many CamelContexts just replace "seda" with "vm" in your URI - they both have the same options.
If you need some examples, there are some here http://svn.apache.org/repos/asf/camel/trunk/camel-core/src/test/java/org/apache/camel/component/vm/
Cheers,
Jon
-
2. Re: VM and SEDA
sriram_imshriram Dec 1, 2009 11:13 AM (in response to sriram_imshriram)I want to use VM end point only to invoke camel contexts across JVMs and the asynchronous behavior it provides is undesired.
Is there a way i could use VM end point to work synchronous?
to(vm:step1).
to(step2)
I want step2 to be executed only the response from step1 is obtained.
I tried using pipeline as
pipeline(vm:step1,step2) but didnt help.
How do we implemene route reuse?
-
3. Re: VM and SEDA
davsclaus Dec 1, 2009 12:04 PM (in response to sriram_imshriram)Camel 2.0 VM allows it to be synchronous
You can specify the option {{waitForTaskToComplete=Always}} to force it to wait for the task on the other VM to complete before continuing.
As it extends the Seda component the options from seda applies to vm as well
-
4. Re: VM and SEDA
sriram_imshriram Dec 2, 2009 6:24 PM (in response to davsclaus)Does this mean that I cannot call a route in another Camel Context synchronously at all in CAMEL < 2.0 , ?
Edited by: sriram on Dec 3, 2009 4:54 AM
-
5. Re: VM and SEDA
davsclaus Dec 3, 2009 2:04 AM (in response to sriram_imshriram)Yes you can for example using JMS, RMI, POJO, using a custom component etc.
All what I am saying is that the VM component is asynchronous only in 1.x