activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (Moved) (JIRA)" <>
Subject [jira] [Moved] (AMQCPP-386) Run-time Setting of Destination Prefix
Date Wed, 08 Feb 2012 21:02:59 GMT


Timothy Bish moved AMQ-3708 to AMQCPP-386:

          Component/s:     (was: CMS (C++ client))
        Fix Version/s:     (was: NEEDS_REVIEWED)
    Affects Version/s:     (was: 5.5.1)
                  Key: AMQCPP-386  (was: AMQ-3708)
              Project: ActiveMQ C++ Client  (was: ActiveMQ)
> Run-time Setting of Destination Prefix
> --------------------------------------
>                 Key: AMQCPP-386
>                 URL:
>             Project: ActiveMQ C++ Client
>          Issue Type: Improvement
>          Components: Stomp
>    Affects Versions: 3.4.1, 3.4.0, 3.3.0
>         Environment: All
>            Reporter: Mark Rappoport
>            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:!default.jspa
For more information on JIRA, see:


View raw message