On Fri, Oct 15, 2010 at 5:25 PM, Donald Whytock wrote:
> Would that be CamelContext.shutdownRoute(id)? And does that use
> RouteDefinition.id() or RouteDefinition.routeId()?
>
The route id, since you are shutting down a route with that given id.
Which you set as follows
...
from("sedq").rout
Would that be CamelContext.shutdownRoute(id)? And does that use
RouteDefinition.id() or RouteDefinition.routeId()?
On Thu, Oct 14, 2010 at 9:24 PM, Willem Jiang wrote:
> 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.
>
> Her
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.
[1]
https://svn.apache.org/repos/asf/camel/trunk/camel-core/src/test/java/org/apache/camel/component/seda/SedaMultipleConsumers
Okay, potentially answering my own question, perhaps DelegateProcessor
would serve for me...
List processors = new ArrayList;
/* add some processors */
DelegateProcessor delegate = new DelegateProcessor(new Pipeline(processors));
Inside a RouteBuilder...
from("seda:queue").process(delegate);
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
handler
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
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
