I was leaving a bit out. It already is split into two routes like you suggest. I've tried doing the inOnly trick as well. I'm using the scala DSL, so I had something like:
A --> B inOnly --> seda:a seda:a -> log It used to do exactly what you say until we upgraded to Camel 2.2 (via a Fuse upgrade). On Thu, Jul 1, 2010 at 7:07 PM, Adrian Trenaman <[email protected]> wrote: > Hmmm... > > Try splitting the route in two: > > 1) A -> B -> seda:log > 2) seda:log -> log:... > > The first route should send the response from B to 'seda:log' and the return > the out message to the endpoint that initiated the route. > > You might need to set the MEP to 'InOnly' for the call to 'seda:log', to > ensure that the route doesn't hang waiting for a response! > > Hope that helps, > Ade > > Open Source Integration: http://fusesource.com > > ----- Original Message ----- > From: crankydillo <[email protected]> > To: [email protected] <[email protected]> > Sent: Thu Jul 01 17:27:50 2010 > Subject: Migrating from 1.6 to 2.2: Using seda endpoint > > 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? > > Thanks. >
