cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Seumas Soltysik (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CXF-2032) JMSCorrelationID set by user causes client to not receive reply
Date Wed, 11 Feb 2009 21:02:59 GMT

    [ https://issues.apache.org/jira/browse/CXF-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672774#action_12672774
] 

Seumas Soltysik commented on CXF-2032:
--------------------------------------

Marat, you are absolutely correct. I missed the logic in JMSFactory which checks configuration
before setting the messageSelector to the conduitID. 

> 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.


Mime
View raw message