Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-4592 Deprecate messaging subsystem
  3. WFLY-4831

Clean up HornetQ modules

    XMLWordPrintable

Details

    • Sub-task
    • Resolution: Done
    • Major
    • 10.0.0.Alpha5
    • None
    • JMS
    • None

    Description

      With the messaging subsystem becoming legacy and its runtime being removed, there is no sense to keep modules for HornetQ server runtime.

      However, we still need modules for:

      • HornetQ client (required for forward protocol compatibility)
      • HornetQ journal (used by other modules such as the transaction subsystem to provide its logging store)

      Attachments

        Issue Links

          relates to

          Task - Represents a small unit of work that is not end-user facing. WFLY-4836 Restore SOAP-over-JMS integration after HornetQ replacement with Apache Active Artemis

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              jmesnil1@redhat.com Jeff Mesnil
              jmesnil1@redhat.com Jeff Mesnil
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: