[
https://issues.apache.org/jira/browse/CXF-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673932#action_12673932
]
Marat Bedretdinov commented on CXF-2032:
----------------------------------------
Christian,
I'm not sure I agree that user provided correlationID should be completely
discounted.
If you have existing JMS/MQ apps participating in the message flow, then we
can't talk ws-addressing, as their logic is most likely already built on
concepts known to JMS and they know nothing/little about WS-*
> JMSCorrelationID set by user causes client to not receive reply
> ---------------------------------------------------------------
>
> Key: CXF-2032
> URL: https://issues.apache.org/jira/browse/CXF-2032
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.1.4
> Reporter: Seumas Soltysik
>
> On the 2.1.x-fixes branch, r709357 made changes to the JMSConduit class which
> uses a UUID that is passed into the JMSFactory class which in turn creates a
> JMSCorrelationID message selector on the JMS Listener using the UUID.
> However, when a user sets a correlation ID on the request, this causes
> JMSListener to fail to find the return message as it is looking for a
> correlation ID based upon the UUID and not based upon the correlation ID set
> by the user.
> There should be a test which tests for the scenario where the user sets the
> correlation ID on the message if it is expected that the user should be able
> to set this value. In my opinion, however, the user should not be able to set
> this value as it will only get them into trouble in they do not choose a
> unique enough ID.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
