JmsMessageReceiverConnection: use of correlationId on request should be configurable [SWS-735]

[gregturn]

Henk Hofman opened SWS-735 and commented

Even if a correlation id is specified on a request message in some cases you might want to use the message id of the request message to be used as correlation id (according to the message id pattern, see: http://download.oracle.com/docs/cd/E13171_01/alsb/docs25/interopjms/MsgIDPatternforJMS.html#wp1046209)

---

Affects: 2.0.2

[gregturn]

Arjen Poutsma commented

You can plug in a MessagePostProcessor into the JmsMessageReceiver, and change the message just before it's sent.

[gregturn]

Henk Hofman commented

Sorry, but that won't do, because you only have the responseMessage in the MessagePostProcessor. To set the messageId of the requestMessage as correlationId on the responseMessage you also need the requestMessage. Do you have any other suggestions to overcome that problem?

[gregturn]

Arjen Poutsma commented

Well, you can always get access to the thread-local transport context, and get access to the request message that way:

TransportContext context = TransportContextHolder.getTransportContext();
JmsReceiverConnection connection = (JmsReceiverConnection) context.getConnection();
Message requestMessage = connection.getRequestMessage();

[gregturn]

Arjen Poutsma commented

Closing old issues