cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jens Granseuer (Created) (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CXF-4148) JMS: Support conduitSelector prefix in combination with using the message ID as correlation ID for asynchronous communication
Date Wed, 29 Feb 2012 15:59:58 GMT
JMS: Support conduitSelector prefix in combination with using the message ID as correlation
ID for asynchronous communication
-----------------------------------------------------------------------------------------------------------------------------

                 Key: CXF-4148
                 URL: https://issues.apache.org/jira/browse/CXF-4148
             Project: CXF
          Issue Type: Improvement
          Components: Transports
    Affects Versions: 2.5.2
            Reporter: Jens Granseuer


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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message