[
https://issues.jboss.org/browse/WFLY-943?page=com.atlassian.jira.plugin.s...
]
Joshua Wilson commented on WFLY-943:
------------------------------------
In the version that I use it does NOT have the "p" and I still get the errors.
For examples please refer to any of the Spring related
[
quickstarts|https://github.com/jboss-developer/jboss-wfk-quickstarts/tree...]
in the JBoss Web Framework Kit quickstarts.
To be clear you need to Build with Eclipse to see the errors.
Does anyone know if this is being worked?
XML schema; use of elementFormDefault='unqualified'; cannot
validate some documents
-----------------------------------------------------------------------------------
Key: WFLY-943
URL:
https://issues.jboss.org/browse/WFLY-943
Project: WildFly
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Documentation
Affects Versions: 8.0.0.Alpha3
Reporter: Elias Ross
Fix For: 8.0.0.CR1
Attachments: jboss-deployment-structure.xml
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