[
https://issues.apache.org/jira/browse/CAMEL-12869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16651564#comment-16651564
]
Dmitry Volodin commented on CAMEL-12869:
----------------------------------------
[~davsclaus] the use case not only related for using a topic as replyTo, it can
be uses for case where source type is topic , but reply type requires as queue.
> ReplyTo destination must match endpoint type (topic or queue) that the
> message is sent on
> -----------------------------------------------------------------------------------------
>
> Key: CAMEL-12869
> URL: https://issues.apache.org/jira/browse/CAMEL-12869
> Project: Camel
> Issue Type: Improvement
> Components: camel-sjms
> Affects Versions: 2.22.1
> Reporter: Shannon Gallagher
> Priority: Major
>
>
> When setting the namedReplyTo attribute on an endpoint, the reply to
> destination always gets created with the same type (topic or queue) as the
> endpoint. When configuring routes using the namedReplyTo in the URI, there is
> no way to make the reply to destination a topic if the endpoint is a queue,
> or a queue if the endpoint is a topic.
> It seems that there should be some way to indicate in the namedReplyTo value
> if the reply to destination should be a topic or queue.
> As an example, I've been looking at the InOutQueueProducerSyncLoadTest and
> seeing that when creating the reply to destination, InOutProducer.java (line
> 93) uses the endpoint's isTopic() value to indicate whether the destination
> should be a topic or a queue. Maybe the topic flag should be determined based
> on the value of namedReplyTo so it does not always have to be the same type
> as the endpoint.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
