[
https://issues.apache.org/jira/browse/CAMEL-14242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16986188#comment-16986188
]
michael elbaz edited comment on CAMEL-14242 at 12/2/19 4:45 PM:
----------------------------------------------------------------
No i think the place is here sorry because i already check the code in past and
it baldly wrong see my comment on github for exemple x-max-priority *must *be
sended as int to rabbitMQ but is sended as String you can try by yourself so
its bugged
was (Author: michael992):
No i don't sorry because i already check the code in past and it baldly wrong
see my comment on github for exemple x-max-priority *must *be sended as int to
rabbitMQ but is sended as String you can try by yourself so its bugged
> Binding parameters is not possible
> ----------------------------------
>
> Key: CAMEL-14242
> URL: https://issues.apache.org/jira/browse/CAMEL-14242
> Project: Camel
> Issue Type: Bug
> Components: camel-rabbitmq
> Affects Versions: 3.0.0
> Reporter: michael elbaz
> Priority: Major
>
> I can' use some rabbitMq parameter eg: *x-max-priority* please provide an
> working exemple.
> It was before possible doing that using deprecated parameter
> *&queueArgsConfigurer=#rabbitMqQueueArgsConfigurer*
> {code:java}
> @Bean("rabbitMqQueueArgsConfigurer")
> public ArgsConfigurer rabbitMqQueueArgsConfigurer() {
> return map -> map.put("x-max-priority", 10);
> }
> {code}
> See this one:
> [https://stackoverflow.com/a/44651087/4271976|https://stackoverflow.com/a/44651087/4271976]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
