On 10/4/07, 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) > > > > > > 2. In the SedaConsumer.run() method. I think the two checks for > > "!isStopping()" should be modified to: "!isStopping() && > > !isStopped()". Otherwise, the consumer's thread can run forever since > > it is possible for ServiceSupport.stop() to change the stopping flag > > to true and back to false before the consumer's thread has a chance to > > check the stopping flag. > > Good catch! Will fix. > > > > > Regards, > > William > > > > > -- > Regards, > Hiram > > Blog: http://hiramchirino.com >
-- Regards, Hiram Blog: http://hiramchirino.com
