I don't want to do anything with the replyChannel per say. I was debugging, trying to figure out why I wasn't getting a response for the message I sent. I configured a gateway and an amqb outbound channel adapter on one end and I was expecting to receive a response generated by the other end. What I was seeing was no response and the message was still in the queue. So I started debugging and found out there was some swallowed exception "The replyTo header must not be null on a request Message being handled by the AMQP inbound gateway." I looked at the message headers and I noticed that header wasn't there. I removed the mapped-request-headers="requestType" attribute and the exception stopped happening. I noticed that the message now had a few headers that I wasn't seeing before.
Originally Posted by Gary Russell
The message header without mapped-request-header:
with the mapped-request-headers I was only seeing:
amqp_contentType=text/plain, amqp_contentEncoding=UTF-8, amqp_deliveryTag=1, amqp_redelivered=false}]
This is what brought me to the conclusion that the default headers were somehow being replaced. If that's not the case, please tell me what I'm doing wrong.
Just for reference, the other side looks like this (omitting the channel defs):
error-channel="errorChannel" mapped-request-headers="requestType" />
<int:mapping value="hello" channel="helloServiceChannel" />
<int:mapping value="goodbye" channel="goodbyeServiceChannel" />
ref="helloService" method="hello" />
ref="goodbyeService" method="goodbye" />