camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Willem Jiang <>
Subject Re: SEDA createConsumer() question
Date Fri, 15 Oct 2010 01:24:01 GMT
In Camel 2.5.0,you can do it by stopping old route which start with the 
SEDA endpoint and adding a new route for it.

Here is an unit test[1] that you can take a look.


On 10/14/10 10:44 PM, Donald Whytock wrote:
> I'm not looking to add an additional consumer; I'm looking to replace
> the existing one.
> In my Chatterbot app, I'm looking to set up a pipeline of message
> handlers in an osgi environment.  I'll have a service that collects
> message handlers and builds a pipeline from them.  But since message
> handlers can come and go, the service will need to be able to rebuild
> the pipeline when a new message handler starts or an existing message
> handler stops.
> What I'd hoped was that if the SEDA queue's endpoint was set up for
> not multiple consumers, creating a new consumer for the endpoint would
> replace the existing consumer.  I take it that that won't
> happen...that instead the new consumer would be ignored?  Is there a
> way to explicitly override the consumers for an endpoint?
> Alternately, is it possible to change the pipeline to use a new List<Consumer>?
> Or am I stuck with tracking the route being added, removing it from
> the context and creating a new one?
> Don
> On Thu, Oct 14, 2010 at 4:00 AM, Willem Jiang<>  wrote:
>> On 10/14/10 3:58 AM, Donald Whytock wrote:
>>> Hi all...
>>> If I have a SEDA endpoint set up for not multiple consumers and I use
>>> createConsumer(processor), will that replace the current consumer?  Or
>>> simply add a consumer that will never be reached?
>>> Don
>> The option of support the multiple consumers if just used to make sure the
>> routes which are added to the camel context should not have the same from
>> endpoint.
>> In Camel 2.5 we fixed an issue[1] of tracking the multiple seda consumers.
>> If you are using Camel 2.4.0, your new added consumer will not be used,
>> [1]
>> --
>> Willem
>> ----------------------------------
>> Open Source Integration:
>> Blog: (English)
>> (Chinese)
>> Twitter:

Open Source Integration:
Blog: (English)

View raw message