CXF
  1. CXF
  2. CXF-4148

JMS: Support conduitSelector prefix in combination with using the message ID as correlation ID for asynchronous communication

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 2.5.2
    • Fix Version/s: None
    • Component/s: Transports
    • Labels:
      None
    • Estimated Complexity:
      Unknown

      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.

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Willem Jiang
            Reporter:
            Jens Granseuer
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:

              Development