Yes, that is what I did in the end as well. I then let the 'main' route
return a 'Ongoing' message using ''. Initially I considered this a
'hack', but I now start to see this as a quite valid solution.
--
View this message in context:
http://camel
tion;
>
> http://localhost:4242/request?synchronous=false"/>
>
> But the call is still "hanging" until the route completes. What am I doing
> wrong?
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Asynchronous-Jetty-tp4
g" until the route completes. What am I doing
wrong?
--
View this message in context:
http://camel.465427.n5.nabble.com/Asynchronous-Jetty-tp474855p5498895.html
Sent from the Camel - Users mailing list archive at Nabble.com.
2009/4/24 Aaron Mulder :
> I have a situation where a request comes in to Jetty, and goes through
> two other routes and queues before a response is generated that allows
> the HTTP response to be sent to the caller. I'd like to be able to
> force Jetty into using continuations so it doesn't park
I have a situation where a request comes in to Jetty, and goes through
two other routes and queues before a response is generated that allows
the HTTP response to be sent to the caller. I'd like to be able to
force Jetty into using continuations so it doesn't park a thread while
those other routes
