-
1. Re: SEDA for asynchronous service invocation
ozkin Feb 20, 2015 12:23 PM (in response to ozkin)Heh.. it seems the fix was too easy but not obvious as many examples show it differently.
Option "waitForTaskToComplete" has to be specified in "to" call and not in "from":
public void configure() {
from("switchyard://TestAsyncCommand").to("seda:async?waitForTaskToComplete=Never");
from("seda:async").log("seda start").delay(10000).log("seda end");
}
Does that sound right for you?
-
2. Re: SEDA for asynchronous service invocation
kcbabo Feb 24, 2015 7:20 PM (in response to ozkin)Yes, that's correct. It's a producer option in the seda component:
The check:
camel/SedaProducer.java at master · apache/camel · GitHub
If Never:
-
3. Re: SEDA for asynchronous service invocation
ozkin Feb 25, 2015 6:40 AM (in response to kcbabo)Ok. Thanks.
Switchyard documentation also lists "waitForTaskToComplete" as an option for SEDA binding. Isn't it then a consumer's property (and not producer's) ?
-
4. Re: SEDA for asynchronous service invocation
kcbabo Feb 25, 2015 8:56 AM (in response to ozkin)Thanks for catching that. Fixed.
-
5. Re: SEDA for asynchronous service invocation
ozkin Feb 25, 2015 3:04 PM (in response to kcbabo)A typo?
The following configuration options are available for binding.file when binding references:
- waitForTaskToComplete
-
6. Re: SEDA for asynchronous service invocation
kcbabo Feb 25, 2015 4:36 PM (in response to ozkin)I don't see any typo.*
* as of 30 seconds ago when I changed it to read binding.seda. Thanks again.