Uploaded image for project: 'JBoss A-MQ'
  1. JBoss A-MQ
  2. ENTMQ-440

rename activemq-broker feature to a-mq-broker to reflect the fabric dependency (or difference from activemq)

    XMLWordPrintable

Details

    • Story
    • Resolution: Done
    • Minor
    • JBoss A-MQ 6.1
    • JBoss A-MQ 6.0
    • broker
    • None

    Description

      from irc:
      bibryam left the chat room. (Ping timeout: 606 seconds)
      [11:27am]ch007m: jstrachan: We have 2 problems when we use JBoss Fuse without fabric & ActiveMQ : 1) bundle mq-fabric must be deployed as there a dependency required by feature activemq-broker & 2) activemq.xml file defines as transporconnector tcp://0.0.0.0:0 --> 0.0.0.0:61626
      [11:42am]gtully: ch007m: the only real differences between a-mq and activemq is that it is fabric aware, so the pid factory from mq-fabric is 'fabric' aware.
      [11:42am]gtully: ch007m: a-mq standalone defines standalone=true in the pid file and defines the openwire.port property to specify 61626. which u can use for 2)
      [11:43am]gtully: maybe we need to rename the features - a-mq-broker to denote the fabric requirement different from activemq-broker (from apache)
      [11:45am]ch007m: gtully: Make sense. Otherwise end users are confused and don't know which features to be used for project using fabric or non fabric

      Attachments

        Issue Links

          Activity

            People

              ggrzybek Grzegorz Grzybek
              gtully@redhat.com Gary Tully
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: