camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <claus.ib...@gmail.com>
Subject Re: choose() question
Date Thu, 16 Sep 2010 17:06:38 GMT
You can use an interceptor and then stop() when to abort.

Or you can set the Exchange.STOP property on the Exchange from a
Processor to tell it to stop


On Thu, Sep 16, 2010 at 7:04 PM, Donald Whytock <dwhytock@gmail.com> wrote:
> Is there something along the lines of an abortable Pipeline, such that
> it will go through a sequence of processors until one of them returns
> a certain value, sets a property on the exchange, etc?
>
> On Thu, Sep 16, 2010 at 12:49 PM, Claus Ibsen <claus.ibsen@gmail.com> wrote:
>> On Thu, Sep 16, 2010 at 6:45 PM, Donald Whytock <dwhytock@gmail.com> wrote:
>>> Hi all...
>>>
>>> Newbie question regarding choose().  Given
>>>
>>> from(endpoint).choose()
>>>  .when(predA).process(processorA)
>>>  .when(predB).process(processorB);
>>>
>>> If predA and predB are both true, do processorA and processorB both
>>> get called?  Or does processing stop with processorA?
>>>
>>
>> Only the first one is chosen. (its not a case, always only 1 at most
>> is selected)
>>
>>
>>> Don
>>>
>>
>>
>>
>> --
>> 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
>>
>



-- 
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

Mime
View raw message