Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-733

Move JMS high-level commands to the messaging extension

    Details

    • Type: Enhancement
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 2.0.0.Alpha3
    • Fix Version/s: 2.0.0.Alpha4
    • Component/s: CLI
    • Labels:
      None

      Description

      the CLI provides jms-queue, jms-topic and connection-factory commands to manage JMS resources.

      These commands are registered in wildfly-cli module and are hard-coded with the /subsystem=messaging address.
      With WildFly 10, the JMS capability will be provided by a new messaging-activemq extension.

      Instead of having to hard-code this again in wildfly-cli module, the JMS commands will instead be loaded by the extension that provides the JMS resources (messaging in a 1st step, messaging-activemq in a 2nd step).

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  jmesnil Jeff Mesnil
                  Reporter:
                  jmesnil Jeff Mesnil
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: