[
https://issues.jboss.org/browse/JBMETA-367?page=com.atlassian.jira.plugin...
]
Joshua Wilson commented on JBMETA-367:
--------------------------------------
In my last comment I wrote about how changing the version makes the error go away in
Eclipse. While this is true it does not actually allow you to deploy the application to
JBoss (where the schema lives).
After looking deeper into this I believe that you are right and that the
elementFormDefault="unqualified" needs to be changed to
elementFormDefault="qualified".
CLONE - XML schema; use of elementFormDefault='unqualified';
cannot validate some documents
-------------------------------------------------------------------------------------------
Key: JBMETA-367
URL:
https://issues.jboss.org/browse/JBMETA-367
Project: JBoss Metadata
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: Elias Ross
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"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira