Camel 2.10 uses # # tokens, so when thats out you wont have this issue.
Also endpoints can be configured using getter/setters, so you may be
able to setup your endpoint without the uri notation.
On Tue, May 22, 2012 at 12:44 PM, camel_user <maxd_...@hotmail.com> wrote:
> Thanks Claus,
>
> I'll try with 2.9.2.
>
> With regards to the thread naming pattern, don't see how this can help as
> the problem is not in the pattern but in the final if statement of
> ThreadHelper class
>
> if (answer.indexOf("$") > -1 || answer.indexOf("${") > -1 ||
> *answer.indexOf("}")* > -1) {
>
> the bit in bold checks for the right curly brace, and since it is present in
> the answer that exception is thrown
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/camel-ThreadHelper-class-failing-to-parse-amqp-topic-x-bindings-tp5713072p5713328.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
