[
https://issues.apache.org/jira/browse/CXF-2760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12857178#action_12857178
]
Willem Jiang commented on CXF-2760:
-----------------------------------
Just a quick note for the jms transport difference of trunk and 2.2.x branch.
Last summer we did some change on the jms transport by leverage the GSoC
project to implement soap of jms, and the change were not merged back to 2.2.x
branch.
If I remember right, the JmsConduit of 2.1.x and 2.2.x should share the same
code.
Seumas, if your patch introduce a new configure property, we should also
support it in the trunk.
> implement useMessageIDAsCorrelationID for JMS Client
> ----------------------------------------------------
>
> Key: CXF-2760
> URL: https://issues.apache.org/jira/browse/CXF-2760
> Project: CXF
> Issue Type: New Feature
> Components: Transports
> Affects Versions: 2.1.4
> Reporter: Seumas Soltysik
> Fix For: 2.1.4
>
> Attachments: cxf-2760.patch
>
>
> MQSeries servers often use the message ID of and incoming message as the
> correlation ID for an outgoing message. In order for a CXF client to
> communicate with an MQSeries server it needs to correlate the outgoing
> message with the incoming message using the message ID of the sent message.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
