Uploaded image for project: 'ActiveMQ C++ Client'
  1. ActiveMQ C++ Client
  2. AMQCPP-590

Some methods in AdvisorySupport return invalid composite destination names

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Not A Problem
    • 3.9.1
    • None
    • CMS Impl, Openwire
    • None

    Description

      These methods return a bad name for the composite destination, all but the first destination lack a topic prefix.

      getTempDestinationCompositeAdvisoryTopic
      getAllDestinationsCompositeAdvisoryTopic

      Attachments

        Activity

          Upon further investigation the methods do return the valid form for OpenWire based transports, for STOMP it is necessary for the user to construct their own version of the composite destination string in order to comply with the STOMP specification requirements.

          tabish Timothy A. Bish added a comment - Upon further investigation the methods do return the valid form for OpenWire based transports, for STOMP it is necessary for the user to construct their own version of the composite destination string in order to comply with the STOMP specification requirements.

          People

            tabish Timothy A. Bish
            tabish Timothy A. Bish
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: