[CXF-4148] JMS: Support conduitSelector prefix in combination with using the message ID as correlation ID for asynchronous communication

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 2.5.2
• Component/s: JMS, Transports
• Estimated Complexity: Unknown
• Assignee: Unassigned
• Reporter: Jens Granseuer
• Created: 29/Feb/12 15:58
• Updated: 20/Apr/17 13:27
• Resolved: 20/Apr/17 13:27

Description

The current implementation only allows using the message ID as a correlation ID and having a conduitSelectorPrefix with synchronous exchanges.

Using a conduitSelectorPrefix is necessary with WebSphereMQ. See also http://cxf.547215.n5.nabble.com/JMS-Message-Correlation-in-CXF-2-3-td4830121.html

This feature has previously been implemented for CXF 2.2 in CXF-2760 but was dropped in the transition to 2.3.