[
https://issues.apache.org/jira/browse/CXF-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672762#action_12672762
]
Marat Bedretdinov commented on CXF-2032:
----------------------------------------
Seumas,
While I agree that there are pieces of missing functionality (namely unable to
select on user provided correlationID unless you use a 'catch all' selector),
I'm not sure if I completely agree to the conclusions.
It could be argued for example that the CXF client can be an intermediary and
needs to relay a third party generated correlation id and the logic in the
third party receiver is predicated on this ID being identical to the original
value.
some source app --1> cxf.consumer --2> cxf.producer --3> some target app
The way things stand right now is the application developer needs to be aware
that if one wants to provide application generated correlationID, then
one has to set <jms:clientConfig useConduitIdSelector="false"/> in WSDL and if
Spring is used then the JMSConfiguration bean takes precedence and <property
name="useConduitIdSelector" value="false"/> has to be set.
This will solve the filed issue, but limits CXF to a shared reply queue per a
single CXF proxy instance. This limitation can be lifted should this become a
requirement with some extra work.
> 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.
