[
https://issues.apache.org/jira/browse/CXF-2760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12857106#action_12857106
]
Christian Schneider commented on CXF-2760:
------------------------------------------
Normally I only do improvements on the trunk and some people from progress
merge the fixes back to the branches. As I currently also have the problem that
I need to talk to a service that returns the message id as the correlation id I
have looked into the trunk if this is already possible.
There you find a boolean messageIdPattern in JmsConduit that is set to true
under certain conditions. I don´t completely understand it but this could also
be a solution for our problem. Sadly this feature is not even in 2.2.7 and I
have no information if or when it is backported.
I think we should discuss this feature on the list if you did not already do
this. It would be interesting what others say about this.
> 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
