Hi
Yeah define it as an endpoint first to have it create the queue with
that factory.
endpoint("seda:x?queueFactory=#myFactor");
from"seda:x")...
Or put the ?queueFactory option on the uris where you use it.
On Wed, Sep 11, 2013 at 1:52 PM, frk <frantisek.kva...@gmail.com> 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:
> http://camel.465427.n5.nabble.com/using-seda-queueFactory-with-shortened-URI-tp5739139.html
> Sent from the Camel Development mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cib...@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
