Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-10339

Broadcast/discovery-group resources have ambiguous requirement specs

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 12.0.0.Final
    • Fix Version/s: 19.0.0.Beta1
    • Component/s: JMS
    • Labels:
      None

      Description

      Currently, the broadcast/discovery-group resources have messy requirement specs, as the capabilities that they require are dependent whether or not the jgroups-cluster attribute is defined.

      I suggest splitting these resources into 2:

      /subsystem=messaging-activemq/server=*/jgroups-broadcast-group=*
      /subsystem=messaging-activemq/server=*/jgroups-discovery-group=*

      which requires clustering capabilities

      and

      /subsystem=messaging-activemq/server=*/socket-broadcast-group=*
      /subsystem=messaging-activemq/server=*/socket-discovery-group=*

      which requires a socket-binding capability.

      This results in clearer requirement specs - which helps simplify the introspection of this subsystem for provisioning purposes.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                ehugonnet Emmanuel Hugonnet
                Reporter:
                pferraro Paul Ferraro
              • Votes:
                0 Vote for this issue
                Watchers:
                9 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: