[
https://issues.apache.org/jira/browse/CAMEL-14242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16987337#comment-16987337
]
Omar Al-Safi commented on CAMEL-14242:
--------------------------------------
Honestly I *don't think* this is a bug, this feature was deprecated in 2.x and
I guess you were aware of it and yet you didn't raise your concerns back then
as Andrea mentioned in the chat. However, I do agree with you that docs are bit
misleading in this regards and wasn't clear on the alternatives.
Second, did you try what I suggested in the chat? To add this in the route
{{arg.queue.x-max-priority=x}} (this is different from what I suggested earlier
as I wasn't really aware)? As I understood from the code, this used to work as
alternative to {{queueArgsConfigurer}}.
Third, we read your comments that you delete in JIRA as email notification,
again this is an open source project, which means we treat each other with
respect and of course constructive criticism is always welcome, hence I again
as I mentioned before we would appreciate the same from you.
> 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)
