[
https://issues.apache.org/jira/browse/CAMEL-14242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16988174#comment-16988174
]
michael elbaz edited comment on CAMEL-14242 at 12/4/19 8:09 PM:
----------------------------------------------------------------
[~omarsmak] i made [some modifications
|https://github.com/apache/camel/pull/3385]it's appear to be work but not sure
at all about side effect, it still not clear for me what's relation between
options and query parameters.
I also detected some weird test see
org.apache.camel.component.rabbitmq.RabbitMQConsumerIntTest.sentMessageIsReceivedWithHeadersRouting()
*// Don't know what it suppose to do but nothing is filtered i get the 3
headers so this test is wrong off course it pass because 1 < 3*
{code:java}
@Test
public void sentMessageIsReceivedWithHeadersRouting() throws
InterruptedException, IOException, TimeoutException {
//should only be one message that makes it through because only
//one has the correct header set
to.expectedMessageCount(1);
Channel channel = connection().createChannel();
channel.basicPublish(HEADERS_EXCHANGE, "", propertiesWithHeader("foo",
"bar"), MSG.getBytes());
channel.basicPublish(HEADERS_EXCHANGE, "", null, MSG.getBytes());
channel.basicPublish(HEADERS_EXCHANGE, "", propertiesWithHeader("foo",
"bra"), MSG.getBytes());
to.assertIsSatisfied();
}
{code}
was (Author: michael992):
[~omarsmak] i made some modifications it's appear to be work but not sure at
all about side effect, it still not clear for me what's relation between
options and query parameters.
I also detected some weird test see
org.apache.camel.component.rabbitmq.RabbitMQConsumerIntTest.sentMessageIsReceivedWithHeadersRouting()
*// Don't know what it suppose to do but nothing is filtered i get the 3
headers so this test is wrong off course it pass because 1 < 3*
{code:java}
@Test
public void sentMessageIsReceivedWithHeadersRouting() throws
InterruptedException, IOException, TimeoutException {
//should only be one message that makes it through because only
//one has the correct header set
to.expectedMessageCount(1);
Channel channel = connection().createChannel();
channel.basicPublish(HEADERS_EXCHANGE, "", propertiesWithHeader("foo",
"bar"), MSG.getBytes());
channel.basicPublish(HEADERS_EXCHANGE, "", null, MSG.getBytes());
channel.basicPublish(HEADERS_EXCHANGE, "", propertiesWithHeader("foo",
"bra"), MSG.getBytes());
to.assertIsSatisfied();
}
{code}
> camel-rabbitmq - Binding parameters with x- is not possible when using
> endpointdsl
> ----------------------------------------------------------------------------------
>
> 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)
