[
https://issues.apache.org/jira/browse/CXF-1978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider resolved CXF-1978.
--------------------------------------
Resolution: Fixed
Just committed a fix.. can you test if this works for you?
> 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
> Assignee: Christian Schneider
> Fix For: 2.0.10, 2.1.4
>
>
> 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.
