[
https://issues.apache.org/jira/browse/CXF-3334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang resolved CXF-3334.
-------------------------------
Resolution: Fixed
Applied patch into trunk and 2.3.x branch.
> cxf-jms should support topicReplyToName option in the JMS URI
> -------------------------------------------------------------
>
> Key: CXF-3334
> URL: https://issues.apache.org/jira/browse/CXF-3334
> Project: CXF
> Issue Type: Improvement
> Components: Transports
> Reporter: Willem Jiang
> Assignee: Willem Jiang
> Fix For: 2.4, 2.3.3
>
>
> According to the URI Scheme for Java(tm) Message Service 1.0, it uses
> the ReplyToName and topicReplyToName for looking up the reply destination.
> {code}
> 4.3.1. Treatment of replyToName parameter
> When used with the "queue" and "topic" variants, the replyToName
> parameter, specified in section 4.1.4, always refers to a name of a
> JMS queue to look up via the Session.createQueue() method. For
> either variant, if a JMS topic is instead required as a response
> destination, a JMS URI can employ the "topicReplyToName" parameter.
> This parameter defines a name to look up with the
> Session.createTopic() method.
> A JMS URI MUST NOT specify both a "topicReplyToName" and a
> "replyToName" parameter.
> {code}
> Current CXF JMS transport implementation just take the parameter of
> "replyToName"
> and look up the destination according to the JMS URI variants.
> We need to honor the "topicReplyToName" parameter for it.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
