[
https://issues.apache.org/jira/browse/CAMEL-14242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16987648#comment-16987648
]
michael elbaz commented on CAMEL-14242:
---------------------------------------
Ok guys after investigate the tests its appear to achieve the same as before
the only way now is by configuring component like this:
{code:java}
private Endpoint rabbitMq() throws Exception {
RabbitMQComponent rabbitMQComponent =
getContext().getComponent("rabbitmq", RabbitMQComponent.class);
rabbitMQComponent.setArgs(Collections.singletonMap("queue.x-max-priority",
"10"));
return rabbitMQComponent.createEndpoint("rabbitmq:foo?queue=foo");
}
{code}
So is working this way but the doc should be updated i think (i personally
prefer the oldest way because we was free to add any option directly using
query parameters and simple map and now like it was the case with
x-max-priority we have to code every options in the component source code).
Thanks for your help
> camel-rabbitmq - Binding parameters with x- 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: Minor
>
> 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)
