You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Christian Schneider (JIRA)" <ji...@apache.org> on 2017/04/20 13:28:04 UTC
[jira] [Closed] (CXF-4148) JMS: Support conduitSelector prefix in
combination with using the message ID as correlation ID for asynchronous
communication
[ https://issues.apache.org/jira/browse/CXF-4148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Schneider closed CXF-4148.
------------------------------------
Resolution: Won't Fix
Assignee: (was: Willem Jiang)
Closing this issue as there has been no activity since 2012. Please reopen if you plan to fix it.
> 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: JMS, 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 was sent by Atlassian JIRA
(v6.3.15#6346)