[
https://issues.apache.org/jira/browse/AMQCPP-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQCPP-386.
---------------------------------
Resolution: Fixed
Fixed on trunk.
> Run-time Setting of Destination Prefix
> --------------------------------------
>
> Key: AMQCPP-386
> URL: https://issues.apache.org/jira/browse/AMQCPP-386
> Project: ActiveMQ C++ Client
> Issue Type: Improvement
> Components: Stomp
> Affects Versions: 3.3.0, 3.4.0, 3.4.1
> Environment: All
> Reporter: Mark Rappoport
> Assignee: Timothy Bish
> Priority: Minor
> Labels: patch
> Fix For: 3.5.0
>
> Attachments: stomp-prefixes.patch
>
>
> Some STOMP-aware message brokers (such as HornetQ) want their destinations
> prefixed in a manner different from "/queue/" or "/topic/". HornetQ, for
> example, wants it to be "jms.queue." or "jms.topic.".
> To address this, I've made some changes to StompHelper, adding the following
> URI parameters:
> * wireFormat.queuePrefix - defaults to "/queue/"
> * wireFormat.topicPrefix - defaults to "/topic/"
> * wireFormat.tempQueuePrefix - defaults to "/temp-queue/"
> * wireFormat.tempTopicPrefix - defaults to "/temp-topic/"
> My patch, however, fails to utilize the framework laid out by the
> StompWireformatProperties class, as the current code structure makes it very
> hard. Regardless, I've tested it with the SimpleProducer example (make sure
> you provide guest/guest as auth params if you're running a vanilla HornetQ)
> and it seems to work fine.
> The patch is against the activemq-cpp-3.4.1 tag as trunk wouldn't compile;
> some formatting issues may be present as well.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira