Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-20984

docs/schema/wildfly-undertow_10_0.xsd got changed since JBoss EAP 7.3

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • 7.4.0.GA
    • 7.4.0.Beta
    • Security, Undertow
    • None
    • False
    • False
    • Undefined

    Description

      With current build of JBoss EAP 7.4.0.Beta-CR1, we can see following difference of docs/schema/wildfly-undertow_10_0.xsd schema since JBoss EAP 7.3.0 release:

      $ diff -u /tmp/jboss-eap-7.3/docs/schema/wildfly-undertow_10_0.xsd wildfly-undertow_10_0.xsd 
--- /tmp/jboss-eap-7.3/docs/schema/wildfly-undertow_10_0.xsd	2020-11-20 10:20:06.000000000 +0100
+++ wildfly-undertow_10_0.xsd	2021-02-03 08:34:56.000000000 +0100
@@ -19,9 +19,12 @@
 <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
            xmlns="urn:jboss:domain:undertow:10.0"
            targetNamespace="urn:jboss:domain:undertow:10.0"
+           xmlns:credential-reference="urn:wildfly:credential-reference:1.0"
            elementFormDefault="qualified"
            attributeFormDefault="unqualified"
            version="1.0">
+
+    <xs:import namespace="urn:wildfly:credential-reference:1.0" schemaLocation="wildfly-credential-reference_1_0.xsd"/>
     <!-- The undertow subsystem root element -->
     <xs:element name="subsystem" type="undertow-subsystemType"/>

      This change has been introduced by this commit that fixed WFLY-13369 (or WFLY-12510 effectively).

      If I understand correctly, based on the discussion in WFLY-12510, the wildfly-undertow_10_0.xsd schema should not been updated at all since it was already present in WildFly 19 release. With this change it was updated and is served with current content till now, see:

      $ find . -name "wildfly-undertow_10*.xsd" | xargs md5sum 
94e642febd4ddb154d91bae2793aa6ef  ./wildfly-21.0.2.Final/docs/schema/wildfly-undertow_10_0.xsd
94e642febd4ddb154d91bae2793aa6ef  ./wildfly-22.0.0.Final/docs/schema/wildfly-undertow_10_0.xsd
94e642febd4ddb154d91bae2793aa6ef  ./wildfly-20.0.1.Final/docs/schema/wildfly-undertow_10_0.xsd
5e1a139844379001efa7bfde6ae26f3b  ./wildfly-19.1.0.Final/docs/schema/wildfly-undertow_10_0.xsd

      To be honest - I am not sure how serious this problem is since effectively there is no functional change in the XSD schema definition - complex types that are brought in by added credential-reference:1.0 dependency schema are already part of the wildfly-undertow_10_0.xsd file. Although, from the customer point of view this change between 7.3.0 and 7.4.0 may be confusing at least.

      Note: Correct value of `Affects Version/s` for this issue should be 7.4.0.Beta-CR1, although there is no such option at the moment.

      Attachments

        Issue Links

          is caused by

          Sub-task - The sub-task of the issue WFLY-13369 Update reference to wildfly-credential-reference_1_1.xsd for future undertow XSD

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          is related to

          Task - Represents a small unit of work that is not end-user facing. WFLY-14427 Fix usages of the credential-reference schema in the Undertow subsystem

          • 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

          Task - Represents a small unit of work that is not end-user facing. WFLY-14788 Fix usages of the credential-reference schema in wildfly-undertow_12_0.xsd

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Activity

            People

              fjuma1@redhat.com Farah Juma
              jstourac@redhat.com Jan Stourac
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: