[
https://issues.apache.org/jira/browse/CXF-1978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12664281#action_12664281
]
Christian Schneider commented on CXF-1978:
------------------------------------------
I have not yet tested it but according to the JMS documentation it should work
like in SQL. So the selector should mean select all messages that start with
the given string. As the correlation id of any message from the Conduit should
start with the given string we should get all messages with only one consumer.
> 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.
