Closed
Description
Cyrille Le Clerc opened SPR-4647 and commented
Enhance MessageListenerAdapter to support "request message id as response correlation id" in addition to the current behavior that use "request correlation id as response correlation id".
"Request JMSMessageID as response JMSCorrelationID" becomes a kind of de-facto standard implementation of the JMS Request/Reply pattern :
- Enterprise Integration Patterns : JMS Request/Reply Example [1]
- Spring WS's JMS transport (see JmsReceiverConnection)
- SOAP over Java Message Service 1.0 RC1 : specification proposal by BEA, IBM, Sonic Software and Tibco [2]
- CXF, Axis2, JAXWS-RI, Websphere, etc use it for their JMS transport
[1] http://enterpriseintegrationpatterns.com/RequestReplyJmsExample.html
[2] http://mail-archives.apache.org/mod_mbox/ws-axis-dev/200701.mbox/raw/%3C80A43FC052CE3949A327527DCD5D6B27020FB65C@MAIL01.bedford.progress.com%3E/3
Affects: 2.5.2
Attachments:
- SPR-4647.patch (14.19 kB)
Issue Links:
- Implement synchronous request / response logic in JmsTemplate [SPR-3332] #8017 Implement synchronous request / response logic in JmsTemplate
2 votes, 3 watchers