-
Bug
-
Resolution: Done
-
Major
-
8.0.0.Alpha3
-
None
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"
- blocks
-
JBIDE-14534 Errors in Spring project archetypes
- Reopened
- is cloned by
-
JBMETA-367 CLONE - XML schema; use of elementFormDefault='unqualified'; cannot validate some documents
- Closed
- is related to
-
JBIDE-14629 Errors when creating and deploying seam2 project with Seam 2.3.Final
- Closed
- relates to
-
WFLY-2858 JPA doesn't parse for "urn:jboss:jpa" namespace in jboss-all.xml
- Closed