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

XSDs should use a correct and existing schemaLocation.

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 8.1.0.Final, 9.0.0.Alpha1
    • Fix Version/s: None
    • Component/s: None
    • Labels:

      Description

      The Feature Request: https://issues.jboss.org/browse/WFLY-3014
      Does not address the actual issue.

      • It is understood that we do not validate the xml with the "schemaLocation". However there are some users who reads the XSD via valid schemaLocation and parse them according to their requirement for XML processing.
      • The XSDs that are shipped with wildfly uses a non existing "schemaLocation". For example: "jboss-web_8_0.xsd"
              <jboss-web xmlns="http://www.jboss.com/xml/ns/javaee"
                 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                 xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-web_8_0.xsd"
                 version="8.0">
      
      	       ...
      
              </jboss-web>
      

      Expectation: Either the XSDs should point to a valid existing URL. Or the XSDs should be corrected to alter the Schema locations from non-existing http://www.jboss.org/j2ee/schema/ (which has very few XSDs) to http://www.jboss.org/schema/jbossas/ (which has almost all the updated xsds)

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                jason.greene Jason Greene
                Reporter:
                jaysensharma Jay SenSharma
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated: