K, I'll try that, but I thought the seda component could did this automagically. What does waitForTaskToComplete=Never mean?
Thanks. On Thu, Jul 1, 2010 at 10:57 PM, Claus Ibsen <[email protected]> wrote: > On Thu, Jul 1, 2010 at 11:27 PM, crankydillo <[email protected]> wrote: >> Hi, >> >> We are processing HTTP requests with a route like A -> B -> seda:log-stuff >> >> Where B produces the actual response that we want sent back to the client. >> >> This used to work in 1.6, but does not in 2.2. I thought the >> waitForTaskToComplete=Never was the answer, but that didn't work either. >> >> Any ideas on how I can get a response back to the client immediately after B >> produces it? > > This is what the WireTap EIP pattern can be used for > http://camel.apache.org/wire-tap > > To tap a message somewhere, such as to the seda queue. > > > >> >> Thanks. >> > > > > -- > 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 >
