[
https://issues.apache.org/jira/browse/CXF-1978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663900#action_12663900
]
Christian Schneider commented on CXF-1978:
------------------------------------------
Hi Ron,
the code you mentioned uses the doReceive function of the JmsTemplate. The
disadvantage of this aproach is that it creates a new consumer for each
request. I would like to keep the style of having one consumer per conduit. I
hope the selector with "like" and a suitable correlationId that has a common
prefix for all messages of the conduit can do this trick.
If this does not work we could of course use doReceive for the case of
permanent queues. But I think this could have a negative impact on performance.
Greetings
Christian
> Spring-based JMS Conduit should support using a shared permanent reply queue
> for several instances
> --------------------------------------------------------------------------------------------------
>
> Key: CXF-1978
> URL: https://issues.apache.org/jira/browse/CXF-1978
> Project: CXF
> Issue Type: Improvement
> Components: Transports
> Affects Versions: 2.0.9, 2.1.3
> Reporter: Ron Gavlin
>
> The new Spring-based JMS Conduit should support using a shared permanent
> reply queue for several instances. The problem with temporary replyTo queues
> is that it is difficult to semantically associate the temporary replyTo
> queues with their original "request" queues. Using a named replyTo queue with
> a selector based on the correlationId solves this problem. This may be
> considered a "regression" introduced during the upgrade from CXF 2.1.2 to
> 2.1.3.
> See Nabble Thread
> http://www.nabble.com/forum/ViewPost.jtp?post=20447067&framed=y.
> /Ron
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
