You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2011/09/14 10:36:08 UTC
[jira] [Resolved] (AMQ-3496) Provide configurable default for
unqualified stomp reply-to header destination string
[ https://issues.apache.org/jira/browse/AMQ-3496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Tully resolved AMQ-3496.
-----------------------------
Resolution: Fixed
resolved in http://svn.apache.org/viewvc?rev=1170474&view=rev
reuse of org.apache.activemq.command.UnresolvedDestinationTransformer
> Provide configurable default for unqualified stomp reply-to header destination string
> -------------------------------------------------------------------------------------
>
> Key: AMQ-3496
> URL: https://issues.apache.org/jira/browse/AMQ-3496
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Transport
> Affects Versions: 5.6.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Priority: Minor
> Fix For: 5.6.0
>
>
> Sending a STOMP message with a test string ("some destination") as the "reply-to" header and ActiveMQ rejected it:
> Illegal destination name: [some destination] -- ActiveMQ STOMP destinations must begin with one of: /queue/ /topic/ /temp-queue/ /temp-topic/
> The JMS specification contains:{quote}
> The JMSReplyTo header field contains a Destination supplied by a client when
> a message is sent. It is the destination where a reply to the message should be
> sent. [...]
> Messages sent with a JMSReplyTo value are typically expecting a response. A
> response may be optional, it is up to the client to decide.{quote}
> Because stomp is layered over jms, we need to default the destination type of any arbitrary string such that the intent is encoded in the destination name.
> Making use of the org.apache.activemq.command.UnresolvedDestinationTransformer from https://issues.apache.org/jira/browse/AMQ-3401 makes sense in this case.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira