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

Correct minOccurts value for host element in XSD

    XMLWordPrintable

Details

    • Workaround Exists
    • Hide

      Add the missing nested <host> element manually in the domain.xml of the target.

      Show
      Add the missing nested <host> element manually in the domain.xml of the target.

    Description

      Broken 'domain.xml' after migration of <host-scoped-roles> leading to 'Boostrap error' in HAL.

      A broken domain configuration

                 <host-scoped-roles>
                <role name="custom-role-name" base-role="Administrator">
                </role>
            </host-scoped-roles>

      This broken configuration doesn't bother the old HAL, so user only see the issue from HAL after the migration.

      The correct one should be:

                  <host-scoped-roles>
                <role name="dbaish" base-role="Administrator">
                    <host name="master"/>
                </role>
            </host-scoped-roles>

      https://github.com/wildfly/wildfly-core/blob/11.0.0.Final/server/src/main/resources/schema/wildfly-config_9_0.xsd#L4567 show minOccurs="1", which is incorrect, the minOccurs should be 0 here.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-17564 [GSS](7.2.z) HAL-1677 - Broken 'domain.xml' after migration of <host-scoped-roles> leading to 'Boostrap error' in HAL

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

          Bug - A problem that impairs or prevents the functions of the product. HAL-1677 Broken console if host list is empty in <host-scoped-roles>

          • 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

              chaowan@redhat.com Chao Wang
              chaowan@redhat.com Chao Wang
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: