camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <>
Subject Re: using seda queueFactory with shortened URI
Date Wed, 11 Sep 2013 13:30:38 GMT

Yeah define it as an endpoint first to have it create the queue with
that factory.


Or put the ?queueFactory option on the uris where you use it.

On Wed, Sep 11, 2013 at 1:52 PM, frk <> wrote:
> Hi,
> found some problem when URI without parameters is used together with new
> seda parameter queueFactory in 2.12.0
> Example route configuration:
> from("seda:a").to("seda:x");
> from("seda:x?queueFactory=#myFactory).log("xxx");
> in this example queue inside of "seda:x?queue=#myQueue" endpoint is the same
> one as the queue created within the "seda:x" endpoint which is a default one
> (LinkedBlockingQueue) and not a queue created by myFactory; if I'm using
> always full URI .to("seda:x?queueFactory=#myFactory) then everything is OK
> seems that using shortened URI is a bad practice and particularly in
> combination of queueFactory parameter it is dangerous and there would be
> appreciated some exception or at least warning that this configuration is
> strange
> thanks and best regards
> Frk
> --
> View this message in context:
> Sent from the Camel Development mailing list archive at

Claus Ibsen
Red Hat, Inc.
Twitter: davsclaus
Author of Camel in Action:

View raw message