We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
In the RequestReplyExample the id is injected in the message being sent.
id
But then the matching process starts and somehow the reply should contain the id as well. Lets say that the reply has a different message format.
For example this is the message sent:
{ "x": 101 }
And this is the message received:
{ "y": 101 }
In the builder you provide I can set the id for the message sent by using it inside the textMessage.
textMessage
amqp("name").requestReply .topicExchange(name = "exchange-name, routingKey = "routing-key") .replyExchange("queue-name") .textMessage("{"x":#{id}}") .messageId("#{id}")
The message being sent is correct and the reply message is also delivered. But this message has some random generated id:
r.t.g.a.a.RequestReply - Message sent user=1 AMQPMessageID=101 r.t.g.a.c.TrackerPool - Message received AmqpMessageID=0aee5b62-cba1-1858-abe5-386b1ba4b412 matchId=0aee5b62-cba1-1858-abe5-386b1ba4b412
How can we parse the value of y in the reply message, in order to be used by the id matching algorithm?
y
The text was updated successfully, but these errors were encountered:
No branches or pull requests
In the RequestReplyExample the
id
is injected in the message being sent.But then the matching process starts and somehow the reply should contain the
id
as well. Lets say that the reply has a different message format.For example this is the message sent:
And this is the message received:
In the builder you provide I can set the
id
for the message sent by using it inside thetextMessage
.The message being sent is correct and the reply message is also delivered. But this message has some random generated id:
How can we parse the value of
y
in the reply message, in order to be used by the id matching algorithm?The text was updated successfully, but these errors were encountered: