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

Broadcast/Discovery group is possible to create with just a name

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 19.0.0.Beta1, 19.0.0.Final
    • 10.0.0.Final, 15.0.0.Final
    • JMS
    • None

    Description

      When defining new broadcast-group in Configuration: Subsystems Subsystem: Messaging - ActiveMQ Messaging Provider: default

      user must define name, at least one connector and then either socket-binding or jgroups-channel-name (not both of them, just one)

      At this moment it's possible to create broadcast group with just a name which is wrong.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-4530 Broadcast/Discovery group is possible to create with just a name

          • 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.
          • Resolved
          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. HAL-1102 Web Console - Messaging - Broadcast should allow to add optional field if there is other required field other than Name

          • 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.
          • Resolved
          is duplicated by

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) WFLY-11005 Requires connectors for broadcast-group resource

          • 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
          relates to

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-1556 Poor handling of 'required', 'nillable' and 'alternatives' in AttributeDefinition

          • 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.
          • Resolved

          Activity

            People

              ehugonne1@redhat.com Emmanuel Hugonnet
              bayern39_jira Chen Maoqian (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: