On 05/10/2007, Hiram Chirino <[EMAIL PROTECTED]> wrote: > On 10/4/07, William Tam <[EMAIL PROTECTED]> wrote: > > 1. In SedaEndpoint.process(Exchange exchange, AsyncCallback callback) > > method. I wouldn't expect callback.done() to be invoked immediately > > when an exchange is enqueued. (right?) But rather I would expect > > callbacks are enqueued with the exchanges so that when the > > SedaConsumer can invoke them after their corresponding exchanges are > > processed. > > I don't agree. I think seda should behave like a jms queue.. The > producer is done when the message gets enqueued. If what you are > trying to do is to do async processing of a pipeline, you should use > the thread processor, like: > from(x).thread(5).to(y)
I wonder; could we have named thread pools using this kinda method? i.e. so a thread pool can just be named in the DSL but then actually defined in size / increase/decrease type stuff separately -- James ------- http://macstrac.blogspot.com/ Open Source SOA http://open.iona.com
