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

XML schema; use of elementFormDefault='unqualified'; cannot validate some documents

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 8.0.0.Final
    • 8.0.0.Alpha3
    • Documentation
    • None

    Description

      When attempting to write a (seemingly) valid jboss-deployment-structure.xml using the schema in ./docs, my document fails to validate.

      This is because of the settings used in the XSD. Have these XSDs been used to validate actual documents? By setting unqualified to 'qualified' then the documents will probably validate.

      $ git grep elementFormDefault..unqualified
      jboss-deployment-dependencies-1_0.xsd: elementFormDefault="unqualified"
      jboss-deployment-structure-1_0.xsd: elementFormDefault="unqualified"
      jboss-deployment-structure-1_1.xsd: elementFormDefault="unqualified"
      jboss-deployment-structure-1_2.xsd: elementFormDefault="unqualified"
      jboss-ejb-client_1_0.xsd: elementFormDefault="unqualified"
      jboss-ejb-client_1_1.xsd: elementFormDefault="unqualified"
      jboss-ejb-client_1_2.xsd: elementFormDefault="unqualified"
      jboss-jpa_1_0.xsd: elementFormDefault="unqualified"

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-14534 Errors in Spring project archetypes

          • 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.
          • Reopened
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBMETA-367 CLONE - XML schema; use of elementFormDefault='unqualified'; cannot validate some documents

          • 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
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-14629 Errors when creating and deploying seam2 project with Seam 2.3.Final

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. WFLY-2858 JPA doesn't parse for "urn:jboss:jpa" namespace in jboss-all.xml

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

              rhn-engineering-rhusar Radoslav Husar
              genman_jira Elias Ross (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: